[Design of JBoss jBPM] - trunk is failing
by ainze
Hi there,
I'm getting following exception when running any test from trunk that involves deploying jpdl:
| org.jbpm.JbpmException: problems during deployment: errors:
|
| error: couldn't parse xml document : java.lang.IllegalArgumentException: When using array of Objects as the value of SCHEMA_SOURCE property , no two Schemas should share the same targetNamespace.
| error: couldn't interpret the dom model: null : java.lang.NullPointerException
| at org.jbpm.pvm.internal.deploy.CheckProblemsDeployer.deploy(CheckProblemsDeployer.java:48)
| at org.jbpm.pvm.internal.deploy.DeployerManager.deploy(DeployerManager.java:61)
| at org.jbpm.pvm.internal.cmd.DeployCmd.execute(DeployCmd.java:54)
| at org.jbpm.pvm.internal.cmd.DeployCmd.execute(DeployCmd.java:1)
| at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
| at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54)
| at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54)
| at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:52)
| at org.jbpm.pvm.internal.svc.ProcessServiceImpl.deploy(ProcessServiceImpl.java:84)
| at org.jbpm.pvm.internal.svc.DeploymentImpl.deploy(DeploymentImpl.java:279)
| at org.jbpm.test.JbpmTestCase.deployJpdlXmlString(JbpmTestCase.java:137)
| at org.jbpm.test.execution.StartExecutionTest.testStartNewExecutionByKey(StartExecutionTest.java:40)
| 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 junit.framework.TestCase.runTest(TestCase.java:154)
| at org.jbpm.test.BaseJbpmTestCase.runTest(BaseJbpmTestCase.java:81)
| at junit.framework.TestCase.runBare(TestCase.java:127)
| at junit.framework.TestResult$1.protect(TestResult.java:106)
| at junit.framework.TestResult.runProtected(TestResult.java:124)
| at junit.framework.TestResult.run(TestResult.java:109)
| at junit.framework.TestCase.run(TestCase.java:118)
| at junit.framework.TestSuite.runTest(TestSuite.java:208)
| at junit.framework.TestSuite.run(TestSuite.java:203)
| 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:460)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
|
|
I'm looking into the problem, but can't find a real cause. Does anyone recognise this error?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220432#4220432
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220432
17 years, 1 month
[Design of JBoss jBPM] - Re: Confused about versioning
by mauromol
"kukeltje" wrote : From what I know there is no functional and api difference between 3.2.x and 3.3.x, so you should be able to use 3.2.x from now on. The only difference was the console afaik....
Actually, these are the differences I could remember:
- the DB schema for 3.3.x has one more column in JBPM_NODE than that of 3.2.x (column PARENTLOCKMODE_)
- some methods were refactorized from 3.2.2 to 3.3.0: for instance org.jbpm.util.ClassLoaderUtil.getProcessClassLoader(ProcessDefinition) was moved to org.jbpm.JbpmConfiguration.getProcessClassLoader(ProcessDefinition)
Unless a "rollback" or a compatibility enhancement between 3.2.x and 3.3.x has been performed, it is not really true that there are no differences between the two branches except for the GWTConsole...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219393#4219393
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219393
17 years, 1 month
[Design of JBoss jBPM] - Re: programmatic passing of environment objects
by tom.baeyens＠jboss.com
"heiko.braun(a)jboss.com" wrote : You can skip the 'finally' when using the callback because it's managed outside of the task service:
|
i don't think so. if the services remain process-engine-context scoped objects, then the callback object would have to be removed just like the provided objects themselves... i think.
internally we only have 1 option:
use a thread local to pass these objects down till the environment is created. in that case the services can remain process-engine-context scoped. if we use thread locals to pass the user provided objects or the callback handlers, that thread local cleanup is also needed for callback handlers.
another alternative would be to create a new service object for each request. but then we would not be able to configure the services. users will not be able to configure customized services. maybe that is an other option to consider. but i don't yet see the full implications of that. feels scary to go that route
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218535#4218535
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218535
17 years, 1 month
