TransactionMixIn cannot be used in a test case in FSW

Solution Unverified - Updated -

Issue

  • The TransactionMixIn cannot be used in a test class, throwing "org.switchyard.SwitchYardException: Unable to bind transaction manager in JNDI".
  • See the test code below:
@RunWith(SwitchYardRunner.class)
@SwitchYardTestCaseConfig(
    config = SwitchYardTestCaseConfig.SWITCHYARD_XML,
    mixins = {CDIMixIn.class, TransactionMixIn.class })
public class TransactionTest {

    private static TransactionMixIn transactionMixIn;

    @BeforeClass
    public static void beforeClass() throws Exception {
        transactionMixIn = new TransactionMixIn();
        transactionMixIn.initialize();
    }

    @Test
    public void testSomething() throws Exception {
        ...
  • And we get the following error stack trace:
org.switchyard.SwitchYardException: Unable to bind transaction manager in JNDI
                at org.switchyard.component.test.mixins.transaction.TransactionMixIn.initialize(TransactionMixIn.java:80)
                at com.example.app.TransactionTest.beforeClass(TransactionTest.java:22)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:597)
                at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
                at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
                at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
                at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
                at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
                at org.switchyard.test.SwitchYardRunner.run(SwitchYardRunner.java:85)
                at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
                at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
                at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
                at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
                at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
                at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
                at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
                at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
                at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
                at javax.naming.InitialContext.bind(InitialContext.java:400)
                at org.switchyard.component.test.mixins.transaction.TransactionMixIn.initialize(TransactionMixIn.java:75)
                ... 17 more

Environment

  • Red Hat JBoss Fuse Service Works (FSW)
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.