org.mule.mule.model

Class MethodHeaderEntryPointResolverTestCase

java.lang.Object

org.mule.tck.junit4.AbstractMuleTestCase

org.mule.tck.junit4.AbstractMuleContextTestCase

org.mule.mule.model.MethodHeaderEntryPointResolverTestCase

public class MethodHeaderEntryPointResolverTestCase
extends AbstractMuleContextTestCase

Nested Class Summary

Nested Classes

Modifier and Type	Class and Description
static class	MethodHeaderEntryPointResolverTestCase.TestFruitCleaner

Field Summary

Fields inherited from class org.mule.tck.junit4.AbstractMuleContextTestCase

callbackCalled, CLASSNAME_ANNOTATIONS_CONFIG_BUILDER, IGNORED_DOT_MULE_DIRS, LOCK_TIMEOUT, muleContext, RECEIVE_TIMEOUT, TEST_MESSAGE, TEST_PAYLOAD, WORKING_DIRECTORY_SYSTEM_PROPERTY_KEY, workingDirectory

Fields inherited from class org.mule.tck.junit4.AbstractMuleTestCase

DEFAULT_TEST_TIMEOUT_SECS, globalTimeout, logger, name, TEST_TIMEOUT_SYSTEM_PROPERTY, TESTING_MODE_PROPERTY_NAME

Constructor Summary

Constructors

Constructor and Description
MethodHeaderEntryPointResolverTestCase()

Method Summary

Methods

Modifier and Type	Method and Description
protected void	doSetUp() Enables the adding of extra behavior on the set up stage of a test right after the creation of the mule context in AbstractMuleContextTestCase.setUpMuleContext().
void	testCustomMethodProperty()
void	testCustomMethodPropertyFail()
void	testMethodPropertyFail()
void	testMethodPropertyMismatch()
void	testMethodPropertyParameterAssignableFromPayload() If a method with correct name is available then it should be used if the parameter type is assignable from the payload type and not just if there is an exact match.
void	testMethodSetPass()
void	testMethodSetWithNoArgsPass()

Methods inherited from class org.mule.tck.junit4.AbstractMuleContextTestCase

addBuilders, configureMuleContext, createMuleContext, createObject, createObject, disposeContext, disposeContextPerTest, doSetUpBeforeMuleContextCreation, doTearDown, doTearDownAfterMuleContextDispose, getBuilder, getConfigurationResources, getFileInsideWorkingDirectory, getNonBlockingResponse, getNonBlockingTestEventUsingFlow, getSensingNullMessageProcessor, getStartUpProperties, getTestConnector, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEventContext, getTestEventContext, getTestEventUsingFlow, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestMuleMessage, getTestMuleMessage, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestService, getTestService, getTestService, getTestSession, getTestTransactedInboundEndpoint, getTestTransformer, getTriggerableMessageSource, getTriggerableMessageSource, getWorkingDirectory, initialiseObject, isDisposeContextPerClass, isGracefulShutdown, isStartContext, setDisposeContextPerClass, setStartContext, setUpMuleContext

Methods inherited from class org.mule.tck.junit4.AbstractMuleTestCase

clearExcludedFlag, clearRequestContext, clearTestCaseName, createTestTimeoutRule, dumpFilteredThreadsInTest, getTestHeader, getTestTimeoutSecs, getTimeoutSystemProperty, initializeMuleTest, isDisabledInThisEnvironment, isDisabledInThisEnvironment, isExcluded, isFailOnTimeout, isOffline, isTestIncludedInExclusionFile, takeTestCaseName

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

MethodHeaderEntryPointResolverTestCase

public MethodHeaderEntryPointResolverTestCase()

Method Detail

doSetUp

protected void doSetUp()
                throws Exception

Description copied from class: AbstractMuleContextTestCase

Enables the adding of extra behavior on the set up stage of a test right after the creation of the mule context in AbstractMuleContextTestCase.setUpMuleContext().

Under normal circumstances this method could be replaced by a @Before annotated method.

Overrides:

doSetUp in class AbstractMuleContextTestCase

Throws:

Exception - if something fails that should halt the test case

testMethodSetPass

public void testMethodSetPass()
                       throws Exception

Throws:

Exception

testMethodSetWithNoArgsPass

public void testMethodSetWithNoArgsPass()
                                 throws Exception

Throws:

Exception

testCustomMethodProperty

public void testCustomMethodProperty()
                              throws Exception

Throws:

Exception

testCustomMethodPropertyFail

public void testCustomMethodPropertyFail()
                                  throws Exception

Throws:

Exception

testMethodPropertyFail

public void testMethodPropertyFail()
                            throws Exception

Throws:

Exception

testMethodPropertyMismatch

public void testMethodPropertyMismatch()
                                throws Exception

Throws:

Exception

testMethodPropertyParameterAssignableFromPayload

public void testMethodPropertyParameterAssignableFromPayload()
                                                      throws Exception

If a method with correct name is available then it should be used if the parameter type is assignable from the payload type and not just if there is an exact match. See MULE-3636.

Throws:

Exception