org.mule.transport.http.issues
Class HttpTransformersMule1815TestCase

java.lang.Object
  org.mule.tck.junit4.AbstractMuleTestCase
      org.mule.tck.junit4.AbstractMuleContextTestCase
          org.mule.tck.junit4.FunctionalTestCase
              org.mule.tck.AbstractServiceAndFlowTestCase
                  org.mule.transport.http.issues.HttpTransformersMule1815TestCase

public class HttpTransformersMule1815TestCase
extends AbstractServiceAndFlowTestCase

Nested Class Summary

Nested classes/interfaces inherited from class org.mule.tck.AbstractServiceAndFlowTestCase

AbstractServiceAndFlowTestCase.ConfigVariant

Field Summary

DynamicPort	dynamicPort1
DynamicPort	dynamicPort2
DynamicPort	dynamicPort3
DynamicPort	dynamicPort4
static String	OUTBOUND_MESSAGE

Fields inherited from class org.mule.tck.AbstractServiceAndFlowTestCase

configResources, variant

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

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

DEFAULT_TEST_TIMEOUT_SECS, globalTimeout, logger, name, TEST_TIMEOUT_SYSTEM_PROPERTY

Constructor Summary

HttpTransformersMule1815TestCase(AbstractServiceAndFlowTestCase.ConfigVariant variant, String configResources)

Method Summary

static Collection<Object[]>	parameters()
void	testAdapted() Adapted model, which should not apply transformers
void	testBase() With no transformer we expect just the modification from the FTC
void	testIgnored() Change in behaviour: transformers are now always applied as part of inbound flow even if component doesn't invoke them.
void	testInbound() But transformers on the base model should be applied

Methods inherited from class org.mule.tck.AbstractServiceAndFlowTestCase

doSetUp, doSetUpForFlow, doSetUpForService, getConfigResources, getTestHeader

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

clearFlowAssertions, getBuilder, getComponent, getComponent, getFlowConstruct, getFunctionalTestComponent, loadResource, loadResourceAsString, stopFlowConstruct, testFlow, testFlow

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

addBuilders, configureMuleContext, createMuleContext, createObject, createObject, disposeContext, disposeContextPerTest, doTearDown, getConfigurationResources, getSensingNullMessageProcessor, getStartUpProperties, getTestConnector, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEventContext, getTestEventContext, getTestEventUsingFlow, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestService, getTestService, getTestService, getTestSession, getTestTransactedInboundEndpoint, getTestTransformer, getTriggerableMessageSource, getTriggerableMessageSource, initialiseObject, isDisposeContextPerClass, isGracefulShutdown, isStartContext, setDisposeContextPerClass, setStartContext, setUpMuleContext

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

clearExcludedFlag, clearRequestContext, createTestTimeoutRule, getTestTimeoutSecs, getTimeoutSystemProperty, initializeMuleTest, isDisabledInThisEnvironment, isDisabledInThisEnvironment, isExcluded, isFailOnTimeout, isOffline, isTestIncludedInExclusionFile

Methods inherited from class java.lang.Object

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

Field Detail

OUTBOUND_MESSAGE

public static final String OUTBOUND_MESSAGE

See Also:

Constant Field Values

dynamicPort1

public DynamicPort dynamicPort1

dynamicPort2

public DynamicPort dynamicPort2

dynamicPort3

public DynamicPort dynamicPort3

dynamicPort4

public DynamicPort dynamicPort4

Constructor Detail

HttpTransformersMule1815TestCase

public HttpTransformersMule1815TestCase(AbstractServiceAndFlowTestCase.ConfigVariant variant,
                                        String configResources)

Method Detail

parameters

public static Collection<Object[]> parameters()

testBase

public void testBase()
              throws Exception

With no transformer we expect just the modification from the FTC

Throws:

Exception

testAdapted

public void testAdapted()
                 throws Exception

Adapted model, which should not apply transformers

Throws:

Exception

testIgnored

public void testIgnored()
                 throws Exception

Change in behaviour: transformers are now always applied as part of inbound flow even if component doesn't invoke them. was: Transformers on the adapted model should be ignored

Throws:

Exception

testInbound

public void testInbound()
                 throws Exception

But transformers on the base model should be applied

Throws:

Exception