[jboss-user] [jBPM Users] - jBPM-4.2 Remote API problem?

markroy do-not-reply at jboss.com
Fri Nov 6 15:25:02 EST 2009


In jBPM 4.1, using the following jbpm.cfg.xml in my simple test app worked:

<jbpm-configuration>
  |   <import resource="jbpm.jbossremote.cfg.xml" />
  | </jbpm-configuration>

Since upgrading to 4.2, however, I now get a NPE:

java.lang.NullPointerException
  | 	at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:177)
  | 	at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.buildProcessEngine(ProcessEngineImpl.java:170)
  | 	at org.jbpm.api.Configuration.getProcessEngine(Configuration.java:161)
  | 	at org.jbpm.test.JbpmTestCase.initialize(JbpmTestCase.java:81)
  | 	at org.jbpm.test.JbpmTestCase.setUp(JbpmTestCase.java:76)
  | 	at gov.faa.ato.esp.ReviewProcess.setUp(ReviewProcess.java:24)
  | 	at junit.framework.TestCase.runBare(TestCase.java:132)
  | 	at junit.framework.TestResult$1.protect(TestResult.java:110)
  | 	at junit.framework.TestResult.runProtected(TestResult.java:128)
  | 	at junit.framework.TestResult.run(TestResult.java:113)
  | 	at junit.framework.TestCase.run(TestCase.java:124)
  | 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
  | 	at junit.framework.TestSuite.run(TestSuite.java:227)
  | 	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
  | 	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)

I traced this to the fact the userCommandService is assigned null from the following:

    userCommandService = (CommandService) processEngineWireContext.get(CommandService.NAME_TX_REQUIRED_COMMAND_SERVICE);

Is this a bug in 4.2, or are there some additional configuration requirements to use the remote API? (I did upgrade the server's db schema to 4.2)





View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264383#4264383

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264383



More information about the jboss-user mailing list