July 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2027) add event listeners

by Tom Baeyens (JIRA)

add event listeners ------------------- Key: JBPM-2027 URL: https://jira.jboss.org/jira/browse/JBPM-2027 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
6
0 / 0

[JBoss JIRA] Updated: (JBPM-1209) support for expressions

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1209?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1209: ------------------------------ Description: this issue incorporates 2 aspects: * review all attributes in jpdl where expression resolving is appropriate. validate with a test. * in the java activity, add the capability to refer to the target object with an expression. that way, the java activity can be used to invoke methods on process variables. > support for expressions > ----------------------- > > Key: JBPM-1209 > URL: https://jira.jboss.org/jira/browse/JBPM-1209 > Project: JBoss jBPM > Issue Type: Feature Request > Reporter: Tom Baeyens > Fix For: jBPM 4.1 > > > this issue incorporates 2 aspects: > * review all attributes in jpdl where expression resolving is appropriate. validate with a test. > * in the java activity, add the capability to refer to the target object with an expression. that way, the java activity can be used to invoke methods on process variables. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2196) unify the retry code in RetryInterceptor and JtaTxInterceptor

by Tom Baeyens (JIRA)

unify the retry code in RetryInterceptor and JtaTxInterceptor ------------------------------------------------------------- Key: JBPM-2196 URL: https://jira.jboss.org/jira/browse/JBPM-2196 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1839) Whenever ActionHandler is executed a new ProcessClassLoader is instantiated

by Thomas Diesler (JIRA)

Whenever ActionHandler is executed a new ProcessClassLoader is instantiated ---------------------------------------------------------------------------- Key: JBPM-1839 URL: https://jira.jboss.org/jira/browse/JBPM-1839 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 4.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

3
2
0 / 0

[JBoss JIRA] Resolved: (JBPM-2087) Verify high volumn job executions with rollback

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2087?page=com.atlassian.jira.plug... ] Tom Baeyens resolved JBPM-2087. ------------------------------- Fix Version/s: (was: jBPM 4.x) Resolution: Out of Date generic load testing has to be introduced instead: JBPM-2310 > Verify high volumn job executions with rollback > ----------------------------------------------- > > Key: JBPM-2087 > URL: https://jira.jboss.org/jira/browse/JBPM-2087 > Project: JBoss jBPM > Issue Type: Task > Components: Runtime Engine > Reporter: Thomas Diesler > > Use JMS instead of DBMS for the store of Jobs. In this case, a Job is not taken by multi-JobExecutors completely. > The configration is mentioned by jBPM Reference Guide in SOA Platform. > http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/JB... > --- Discussion Summary --- > There are two separate places where locking is an issue. > * Job acquisition > * Join node > The join node already supports pessimistic locking, whereas job acquisition *under the job executor* does not. On the other hand, under JMS, job acquisition does not exhibit any locking issue because each job is a separate message. The container deals with distributing the messages among the pool of JobListenerBean instances. > Using JMS will remove the clashes, at least from the perspective of the job executor. Supporting the JMS feature negates the need for pessimistic locking during job acquisition. > Given the above points, if JBPM-1952 is fully supported then JBPM-1953 becomes unnecessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2068) database conversion support

by Tom Baeyens (JIRA)

database conversion support --------------------------- Key: JBPM-2068 URL: https://jira.jboss.org/jira/browse/JBPM-2068 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Baeyens -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2019) Migrate/respect existing spring integration

by Heiko Braun (JIRA)

Migrate/respect existing spring integration -------------------------------------------- Key: JBPM-2019 URL: https://jira.jboss.org/jira/browse/JBPM-2019 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Engine Reporter: Heiko Braun Fix For: jBPM 4.0.x http://jira.springframework.org/browse/MOD-297 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBPM-165) process instance versioning

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Tom Baeyens updated JBPM-165: ----------------------------- Fix Version/s: jBPM 4.1 (was: jBPM 4.x) > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Runtime Engine > Reporter: Tom Baeyens > Fix For: jBPM 4.1 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. > NOTE: i believe that Bernd has got some code for this in jBPM 3. That could be used as a basis. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2391) Incorrect mapping of multiplicity attribute for join activities

by Kevin Wetzels (JIRA)

Incorrect mapping of multiplicity attribute for join activities --------------------------------------------------------------- Key: JBPM-2391 URL: https://jira.jboss.org/jira/browse/JBPM-2391 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Kevin Wetzels The "multiplicity" attribute of a join activity is spelled wrong in org.jbpm.jpdl.internal.activity.JoinBinding. It reads "multiplicicty" at lines 42 and 43. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2394) Java Activities cannot be be async when the method takes an argument (at least on the spring context).

by Robert Moskal (JIRA)

Java Activities cannot be be async when the method takes an argument (at least on the spring context). ------------------------------------------------------------------------------------------------------ Key: JBPM-2394 URL: https://jira.jboss.org/jira/browse/JBPM-2394 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.CR1 Environment: java-6-sun-1.6.013. The app is a unit test set up after Andres Inze's examples here http://www.inze.be/andries/2009/05/24/spring-integration-part-of-jbpm4-tr... Reporter: Robert Moskal I have been testing the spring integration code in the trunk, though I think this has nothing to do with Spring. If I run a test that simply starts a process that has an async node with a bean with a method that takes no argument it runs to the end just as yuo would expect. <process name="TopTake2" xmlns="http://jbpm.org/4.0/jpdl"> <start g="69,143,48,48" name="TopSubFlow"> <transition to="entryNotifications"/> </start> <java expr="#{notificationService}" g="169,146,80,40" method="notify1" name="entryNotifications" async="true"> <transition to="end1" g="-49,-22"/> </java> <end name="end1" g="296,144,48,48"/> </process> However, if I change the description a little to call a method that takes an argument, like so I get an xml validation error saying that async is not allowed to appear in element java (the trace is below): <process name="TopTake2" xmlns="http://jbpm.org/4.0/jpdl"> <start g="69,143,48,48" name="TopSubFlow"> <transition to="entryNotifications"/> </start> <java expr="#{notificationService}" g="169,146,80,40" method="notify1" name="entryNotifications" async="true"> <arg value="hi"/> <transition to="end1" g="-49,-22"/> </java> <end name="end1" g="296,144,48,48"/> </process> org.jbpm.api.JbpmException: xml validation error: cvc-complex-type.3.2.2: Attribute 'async' is not allowed to appear in element 'java'. [line=7 column=114 ]: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'async' is not allowed to appear in element 'java'. error: arg must contain exactly one descriptor element out of [task-service, transaction, char, hibernate-session, long, float, hibernate-configuration, execution-service, byte, jboss-idm-identity-session-factory, mail-session, false, db-session, command-service, message-session, seam-hibernate-session, job-executor, jboss-idm-identity-session, repository-session, int, class, properties, double, transaction-ref, repository-service, script-manager, deployer-manager, identity-service, management-service, authorization-interceptor, business-calendar, job-test-helper, repository-cache, hibernate-session-factory, set, timer-session, env-ref, object, address-resolver, short, map, types, jndi, history-service, null, identity-session, jpdl-deployer, context-ref, true, list, env, history-session, process-engine-ref, ref, authentication, string, id-generator, mail-template] as contents:<java async="true" continue="sync" expr="#{notificationService}" g="169,146,80,40" method="notify1" name="entryNotifications" xmlns="http://jbpm.org/4.0/jpdl"> <arg value="hi"/> <transition g="-49,-22" to="end1"/> </java> [line=8 column=21 ] at org.jbpm.pvm.internal.xml.ProblemList.getJbpmException(ProblemList.java:168) at org.jbpm.pvm.internal.xml.ProblemList.getJbpmException(ProblemList.java:141) at org.jbpm.pvm.internal.repository.DeployerManager.deploy(DeployerManager.java:50) at org.jbpm.pvm.internal.repository.RepositorySessionImpl.deploy(RepositorySessionImpl.java:55) at org.jbpm.pvm.internal.cmd.DeployCmd.execute(DeployCmd.java:46) at org.jbpm.pvm.internal.cmd.DeployCmd.execute(DeployCmd.java:32) at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42) at org.jbpm.pvm.internal.spring.CommandTransactionCallback.doInTransaction(CommandTransactionCallback.java:50) at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:127) at org.jbpm.pvm.internal.tx.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:79) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55) at org.jbpm.pvm.internal.repository.DeploymentImpl.deploy(DeploymentImpl.java:89) at org.jbpm.test.AbstractTransactionalSpringJbpmTestCase.deployJpdlFromClasspath(AbstractTransactionalSpringJbpmTestCase.java:100) at com.bluesky.skyline.workflow.toplevel.TestWiring.onSetUpInTransaction(TestWiring.java:23) at org.springframework.test.AbstractTransactionalSpringContextTests.onSetUp(AbstractTransactionalSpringContextTests.java:176) at org.springframework.test.AbstractSingleSpringContextTests.setUp(AbstractSingleSpringContextTests.java:89) at junit.framework.TestCase.runBare(TestCase.java:125) at org.springframework.test.ConditionalTestCase.runBare(ConditionalTestCase.java:69) 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) Caused by: org.jbpm.api.JbpmException at org.jbpm.pvm.internal.xml.ProblemList.getJbpmException(ProblemList.java:164) ... 30 more Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'async' is not allowed to appear in element 'java'. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jbpm.pvm.internal.xml.Parser.buildDom(Parser.java:451) at org.jbpm.pvm.internal.xml.Parser.execute(Parser.java:387) at org.jbpm.pvm.internal.xml.Parse.execute(Parse.java:157) at org.jbpm.jpdl.internal.repository.JpdlDeployer.deploy(JpdlDeployer.java:60) at org.jbpm.pvm.internal.repository.DeployerManager.deploy(DeployerManager.java:46) ... 28 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2009