April 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1108) create ws interface for retrieving data stored in the jBPM logs

by Vitaliy Kotov (JIRA)

create ws interface for retrieving data stored in the jBPM logs --------------------------------------------------------------- Key: JBPM-1108 URL: http://jira.jboss.com/jira/browse/JBPM-1108 Project: JBoss jBPM Issue Type: Sub-task Reporter: Vitaliy Kotov Assigned To: Tom Baeyens -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-1115) Broken datamodel when a detached ProcInst is saved

by Britt Miner (JIRA)

Broken datamodel when a detached ProcInst is saved -------------------------------------------------- Key: JBPM-1115 URL: http://jira.jboss.com/jira/browse/JBPM-1115 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Britt Miner Assigned To: Tom Baeyens I've noticed (accidentally of course, -ahem-) that if you attempt to call jbpmContext.save(processInstance) on a pi that was loaded outside of the current session, Hibernate will save a new pi with a new Id--however it will reference the same rootToken, etc. as the original pi, and all kinds of unexpected behavior quietly ensues. Of course, loading a fresh copy of the pi immediately before you do anything with it avoids the problem; however, a lot of serious data integrity hangs on remembering to do that every time. (for instance, when a pi being viewed in a UI is injected into an action component, the programmer must remember to load up a fresh copy before working on it.) Since failing to re-load a detached pi can result in what seems to be a broken jBPM data model, jBPM should probably be doing something itself to avoid the problem. I think there are possibly two ways to prevent this from happening: 1) Simply changing the HibernateSaveOperation.save(processInstance) method to saveOrUpdate() seems to perform cleanly. 2) Do a check on the pi, and throw an error if it doesn't belong to the current hibernate session. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1114) If a node is set to async the console does not seem to report which node has the focus in the process.

by Kurt Stam (JIRA)

If a node is set to async the console does not seem to report which node has the focus in the process. ------------------------------------------------------------------------------------------------------ Key: JBPM-1114 URL: http://jira.jboss.com/jira/browse/JBPM-1114 Project: JBoss jBPM Issue Type: Bug Reporter: Kurt Stam Assigned To: Tom Baeyens Priority: Minor Attachments: async=true on all nodes..jpg I'm deploying 1 jPDL with all nodes having the attribute async="true" and one where I left the node synchronous. When I now start the a process instance the async one does not show a focus on the "Review Order" while the other one does. See the attached screenshots. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1126) ProcessDeifnition substates load into top level node list

by James Violette (JIRA)

ProcessDeifnition substates load into top level node list --------------------------------------------------------- Key: JBPM-1126 URL: http://jira.jboss.com/jira/browse/JBPM-1126 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: ANY Reporter: James Violette Assigned To: Tom Baeyens Priority: Minor The ProcessDefinition.hbm.xml nodes list must have a where clause to avoid loading substate nodes into the top level node list. The released nodes list definition <list name="nodes" cascade="all"> <cache usage="nonstrict-read-write"/> <key column="PROCESSDEFINITION_" /> <list-index column="NODECOLLECTIONINDEX_" /> <one-to-many class="org.jbpm.graph.def.Node" /> </list> should be <list name="nodes" cascade="all" where="superstate is null" > <cache usage="nonstrict-read-write"/> <key column="PROCESSDEFINITION_" /> <list-index column="NODECOLLECTIONINDEX_" /> <one-to-many class="org.jbpm.graph.def.Node" /> </list> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1133) the query findActiveNodesByProcessInstance doesn't find active nodes in the root token

by jerome tellier (JIRA)

the query findActiveNodesByProcessInstance doesn't find active nodes in the root token -------------------------------------------------------------------------------------- Key: JBPM-1133 URL: http://jira.jboss.com/jira/browse/JBPM-1133 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: jerome tellier Assigned To: Tom Baeyens Priority: Minor the query findActiveNodesByProcessInstance has the condition "token.parent is not null", but if the token is the root token his parent is null. the query needs certainly also a "distinct". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1145) Loops realized via a decision node will eventually cause a StackOverflow Exception

by R??diger Schmitz (JIRA)

Loops realized via a decision node will eventually cause a StackOverflow Exception ---------------------------------------------------------------------------------- Key: JBPM-1145 URL: http://jira.jboss.com/jira/browse/JBPM-1145 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4, jBPM 3.1 Reporter: R??diger Schmitz Assigned To: Tom Baeyens Executing a simple, iterative loop implemented with a decision node will cause a StackOverflowException (see below for stacktrace). Apparently the iterative calls are executing using recursive calls. This approach fails if a medium sized loop should be executed (a simple reproducing testcase only reached 161 loop iterations before failing). I see this implementation style as highly problematic when processing medium-sized quantities of input data... java.lang.StackOverflowError at java.lang.ClassLoader.findBootstrapClass(Native Method) at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:891) at java.lang.ClassLoader.loadClass(ClassLoader.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.hibernate.loader.Loader.loadCollection(Loader.java:1926) at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627) at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) at org.hibernate.collection.PersistentList.iterator(PersistentList.java:115) at org.jbpm.graph.def.GraphElement.findExceptionHandler(GraphElement.java:358) at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:326) at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:343) at org.jbpm.graph.def.Node.execute(Node.java:332) at org.jbpm.graph.def.Node.enter(Node.java:316) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) <snip>...a ton of repeating stacktraceelements omitted... <snap> at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$cb94b78_3.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:119) at org.jbpm.graph.def.Node.leave(Node.java:382) at org.jbpm.graph.exe.ExecutionContext.leaveNode(ExecutionContext.java:136) at org.jbpm.graph.node.Decision.execute(Decision.java:145) at org.jbpm.graph.def.Node.enter(Node.java:316) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$cb94b78_3.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:119) at org.jbpm.graph.def.Node.leave(Node.java:382) at org.jbpm.graph.def.Node.leave(Node.java:346) at org.jbpm.graph.exe.ExecutionContext.leaveNode(ExecutionContext.java:120) at com.atos.worldline.kams.workflow.pf.BusinessObjectAccessHandler.doExecute(BusinessObjectAccessHandler.java:114) at com.atos.worldline.kams.workflow.pf.AbstractBusinessMethodHandler.execute(AbstractBusinessMethodHandler.java:60) at org.jbpm.graph.def.Action.execute(Action.java:123) at org.jbpm.graph.def.Action$$FastClassByCGLIB$$7876e90e.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Action$$EnhancerByCGLIB$$889386ac_3.execute(<generated>) at org.jbpm.graph.def.Node.execute(Node.java:328) at org.jbpm.graph.def.Node.enter(Node.java:316) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$cb94b78_3.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:119) at org.jbpm.graph.def.Node.leave(Node.java:382) at org.jbpm.graph.exe.ExecutionContext.leaveNode(ExecutionContext.java:136) at org.jbpm.graph.node.Decision.execute(Decision.java:145) at org.jbpm.graph.def.Node.enter(Node.java:316) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$cb94b78_3.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:119) at org.jbpm.graph.def.Node.leave(Node.java:382) at org.jbpm.graph.def.Node.leave(Node.java:346) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-1095) jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo)

by Len DiMaggio (JIRA)

jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo) ------------------------------------------------------------------------------------------- Key: JBPM-1095 URL: http://jira.jboss.com/jira/browse/JBPM-1095 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Len DiMaggio Assigned To: Tom Baeyens jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo) http://jira.jboss.com/jira/browse/SOA-196 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1127) enterprise module testable against different databases

by Aleksandar Kostadinov (JIRA)

enterprise module testable against different databases ------------------------------------------------------ Key: JBPM-1127 URL: http://jira.jboss.com/jira/browse/JBPM-1127 Project: JBoss jBPM Issue Type: Task Affects Versions: jBPM 3.2.2 SOA 1 Reporter: Aleksandar Kostadinov Assigned To: Tom Baeyens Fix For: jBPM 3.2.2 SOA 1 jpdl module is testable against databases. identity module can be tested with different databases just altering the classpath to point to the database configuration. Now enterprise module can't be tested with different DB other than hsqldb that easy. The immediate problem is calling the package target in the jboss/configuration directory where it generates hypersonic database script by default. Changing the classpath of the JBPM taskdef task in jpdl/examples/build.xml to include database driver and database configuration produces an error: /qa/services/hudson/hudson_workspace/workspace/jboss-soa-platform-JBPM.3-testsuite/jbpm.3/jpdl/examples/build.xml:167: /qa/services/hudson/hudson_workspace/workspace/jboss-soa-platform-JBPM.3-testsuite/jbpm.3/jpdl/examples/target/db not found. So obviously changes to jpdl/examples will be needed as well database driver will need to be included into the generated package and I don't know what else. We need that change to test the SOA-P distribution of JBPM against the supported databases so the change needs to be applied to the SOA-P branch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1143) Decision Nodes not working, exception says decision selected non existing transition - reference SOA-450

by Jeff DeLong (JIRA)

Decision Nodes not working, exception says decision selected non existing transition - reference SOA-450 -------------------------------------------------------------------------------------------------------- Key: JBPM-1143 URL: http://jira.jboss.com/jira/browse/JBPM-1143 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: T60 laptop running RHEL 5, Java 1.5, SOA Platform 4.2 CR3 Reporter: Jeff DeLong Assigned To: Tom Baeyens I have defined a process definition with the following decision node where Account is a POJO. I can see that the Account as a jBPM variable in the jBPM Admin Console. <decision name="Sufficient Funds in Account?" expression="#{account.balance > tollTransaction.toll} "> <transition to="Post Toll Transaction to Account" name="true"></transition> <transition to="Replenish Account" name="false"></transition> </decision> When I execute the process, I get the following errors: 15:55:39,123 ERROR [GraphElement] action threw exception: decision 'Sufficient Funds in Account?' selected non existing transition 'true ' org.jbpm.JbpmException: decision 'Sufficient Funds in Account?' selected non existing transition 'true ' at org.jbpm.graph.node.Decision.execute(Decision.java:102) at org.jbpm.graph.def.Node.enter(Node.java:319) 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:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$b7f2fc0f.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:151) at org.jbpm.graph.def.Node.leave(Node.java:394) 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:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$b7f2fc0f.leave(<generated>) at org.jbpm.graph.exe.Token.signal(Token.java:195) at org.jbpm.graph.exe.Token.signal(Token.java:140) 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:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$e74c698b.signal(<generated>) at org.jbpm.command.SignalCommand.execute(SignalCommand.java:91) at org.jboss.soa.esb.services.jbpm.cmd.AsyncProcessSignal$AsyncSignalAction.execute(AsyncProcessSignal.java:287) at org.jbpm.graph.def.Action.execute(Action.java:122) 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:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Action$$EnhancerByCGLIB$$b15cf56b.execute(<generated>) at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:264) 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:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$b7f2fc0f.executeAction(<generated>) at org.jbpm.job.ExecuteActionJob.execute(ExecuteActionJob.java:32) 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:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.job.Job$$EnhancerByCGLIB$$27ab04c8.execute(<generated>) at org.jbpm.job.executor.JobExecutorThread.executeJob(JobExecutorThread.java:164) at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:64) I then tried the following (simpler) expression, and got a similar result: #{account.balance > 100} 16:07:28,807 ERROR [GraphElement] action threw exception: decision 'Sufficient Funds in Account?' selected non existing transition 'false ' org.jbpm.JbpmException: decision 'Sufficient Funds in Account?' selected non existing transition 'false ' -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBPM-1112) <mail> action not allowed in <timer>

by Tong Zheng (JIRA)

<mail> action not allowed in <timer> ------------------------------------ Key: JBPM-1112 URL: http://jira.jboss.com/jira/browse/JBPM-1112 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: JDK 1.5, jPDL 3.2.2 Reporter: Tong Zheng Assigned To: Tom Baeyens It's mentioned in the doc that "Anywhere you are allowed to specify actions in the process, you can specify a mail action". But mail action doesn't work inside timer. sample code: <state name="resolve-issue"> <event type="node-enter"> <mail name="notification" to="user1@localhost" template="notification"> </mail> </event> <timer name="timer-reminder-1" duedate="5 seconds"> <mail name="reminder-1" to="user1@localhost" template="reminder"> </mail> </timer> <transition to="end"></transition> </state> Got exception while deploying the definition: org.jbpm.jpdl.JpdlException: [[ERROR] line 20: cvc-complex-type.2.4.a: Invalid content was found starting with element 'mail'. One of '{"urn:jbpm.org:jpdl-3.2":action, "urn:jbpm.org:jpdl-3.2":script}' is expected.] at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:172) at org.jbpm.graph.def.ProcessDefinition.parseXmlInputStream(ProcessDefinition.java:180) at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:161) at org.albertahealth.waitlist.workflow.app.DeployProcess.deployProcessFromXml(DeployProcess.java:61) at com.albertahealth.waitlist.workflow.app.DeployEWProcessTest.testDeployProcessDefinition(DeployEWProcessTest.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:154) 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:128) 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) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

5
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues April 2008