February 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-1210) spring configuration support

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1210?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1210: ----------------------------------- andries, do you also have a normal zip file ? > spring configuration support > ---------------------------- > > Key: JBPM-1210 > URL: https://jira.jboss.org/jira/browse/JBPM-1210 > Project: JBoss jBPM > Issue Type: Feature Request > Components: PVM > Reporter: Tom Baeyens > Assignee: Mauricio Salatino > Priority: Minor > Fix For: jBPM 4.0.x > > Attachments: spring-jbpm-v1.7z > > > The first goal is to create an EnvironmentFactory implementation that is based on spring configuration. > The class to complete is org.jbpm.pvm.internal.env.SpringEnvironmentFactory > The SpringEnvironmentFactory should relate to a spring ApplicationContext, I believe. The first thing to do is create a test that shows how a spring configuration can be used to create hibernate sessions. > Something like this: > static EnvironmentFactory environmentFactory = SpringEnvironmentFactory.parseResource("org/jbpm/pvm/spring/springbeans.xml"); > Environment environment = environmentFactory.openEnvironment(); > try { > Session hibernateSession = environment.get(Session.class); > assertNotNull(hibernateSession); > } finally { > environment.close(); > } -- 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, 10 months

1
0
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: ----------------------------- Description: 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. was: 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. Fix Version/s: jBPM 4.0.x > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Fix For: jBPM 4.0.x > > > 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

15 years, 10 months

1
0
0 / 0

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

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Tom Baeyens reopened JBPM-165: ------------------------------ > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > > 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. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1842) ESB Batch transaction capability

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1842?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1842: ------------------------------ > ESB Batch transaction capability > -------------------------------- > > Key: JBPM-1842 > URL: https://jira.jboss.org/jira/browse/JBPM-1842 > Project: JBoss jBPM > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-2009) Supply a jPDL 4 schema

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2009?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-2009: ------------------------------ > Supply a jPDL 4 schema > ---------------------- > > Key: JBPM-2009 > URL: https://jira.jboss.org/jira/browse/JBPM-2009 > Project: JBoss jBPM > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Heiko Braun > Assignee: 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1210) spring configuration support

by Andries Inze (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1210?page=com.atlassian.jira.plug... ] Andries Inze updated JBPM-1210: ------------------------------- Attachment: spring-jbpm-v1.7z I've created an example jbpm-spring integration module. It's not perfect, but a direction for future implementations. The filename is uploaded as attachment under jbpm-spring-v1.7z . It comes with following features: * Injection of a Spring configured Hibernate SessionFactory, * AbstractTransactionSpringJbpmTestCase which is a transactional testcase. I believe that for Spring integration, jBPM should refrain from running its own transaction management, since Spring will handle this. This class should be enhanced with more The jbpm configuration is slightly altered, removing the transaction interceptor, session factory and setting the current="true" on the session. I'm looking forward to any feedback! > spring configuration support > ---------------------------- > > Key: JBPM-1210 > URL: https://jira.jboss.org/jira/browse/JBPM-1210 > Project: JBoss jBPM > Issue Type: Feature Request > Components: PVM > Reporter: Tom Baeyens > Assignee: Mauricio Salatino > Priority: Minor > Fix For: jBPM 4.0.x > > Attachments: spring-jbpm-v1.7z > > > The first goal is to create an EnvironmentFactory implementation that is based on spring configuration. > The class to complete is org.jbpm.pvm.internal.env.SpringEnvironmentFactory > The SpringEnvironmentFactory should relate to a spring ApplicationContext, I believe. The first thing to do is create a test that shows how a spring configuration can be used to create hibernate sessions. > Something like this: > static EnvironmentFactory environmentFactory = SpringEnvironmentFactory.parseResource("org/jbpm/pvm/spring/springbeans.xml"); > Environment environment = environmentFactory.openEnvironment(); > try { > Session hibernateSession = environment.get(Session.class); > assertNotNull(hibernateSession); > } finally { > environment.close(); > } -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1981) Example tests fail

by Heiko Braun (JIRA)

Example tests fail ------------------ Key: JBPM-1981 URL: https://jira.jboss.org/jira/browse/JBPM-1981 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Reporter: Heiko Braun Assignee: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 These tests fail Tests in error: testScriptText(org.jbpm.examples.script.expression.ScriptExpressionTest) testConcurrencyGraphBased(org.jbpm.examples.concurrency.graphbased.ConcurrencyGraphBasedTest) testEndProcessInstance(org.jbpm.examples.end.processinstance.EndProcessInstanceTest) testJavaInstantiate(org.jbpm.examples.java.JavaInstantiateTest) testExclusiveHandlerGreat(org.jbpm.examples.exclusive.handler.ExclusiveHandlerTest) testExclusiveHandlerImprove(org.jbpm.examples.exclusive.handler.ExclusiveHandlerTest) testExclusiveHandlerSuck(org.jbpm.examples.exclusive.handler.ExclusiveHandlerTest) testEsb(org.jbpm.examples.esb.EsbTest) testStateChoiceAccept(org.jbpm.examples.state.choice.StateChoiceTest) testStateChoiceReject(org.jbpm.examples.state.choice.StateChoiceTest) testSql(org.jbpm.examples.sql.SqlTest) testHql(org.jbpm.examples.hql.HqlTest) testEndMultipleOk(org.jbpm.examples.end.multiple.EndMultipleTest) testEndMultipleBadRequest(org.jbpm.examples.end.multiple.EndMultipleTest) testEndMultipleInternalServerError(org.jbpm.examples.end.multiple.EndMultipleTest) testScriptText(org.jbpm.examples.script.text.ScriptTextTest) testExclusiveConditionsGood(org.jbpm.examples.exclusive.conditions.ExclusiveConditionsTest) testExclusiveConditionsBad(org.jbpm.examples.exclusive.conditions.ExclusiveConditionsTest) testExclusiveConditionsUgly(org.jbpm.examples.exclusive.conditions.ExclusiveConditionsTest) testWaitStatesSequence(org.jbpm.examples.state.sequence.StateSequenceTest) testTask(org.jbpm.examples.task.TaskTest) testEndStateCompleted(org.jbpm.examples.end.state.EndStateTest) testEndStateErrorBadRequest(org.jbpm.examples.end.state.EndStateTest) testEndStateErrorInternalServerError(org.jbpm.examples.end.state.EndStateTest) testExclusiveExpressionGood(org.jbpm.examples.exclusive.expression.ExclusiveExpressionTest) testExclusiveExpressionBad(org.jbpm.examples.exclusive.expression.ExclusiveExpressionTest) testExclusiveExpressionUgly(org.jbpm.examples.exclusive.expression.ExclusiveExpressionTest) due to ------------------------------------------------------------------------------- Test set: org.jbpm.examples.script.expression.ScriptExpressionTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.272 sec <<< FAILURE! testScriptText(org.jbpm.examples.script.expression.ScriptExpressionTest) Time elapsed: 0.225 sec <<< ERROR! java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:675) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:316) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:280) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at javax.script.ScriptEngineManager.<init>(ScriptEngineManager.java:65) at javax.script.ScriptEngineManager.<init>(ScriptEngineManager.java:49) at org.jbpm.pvm.internal.wire.binding.ScriptManagerBinding.parse(ScriptManagerBinding.java:80) -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1963) build jbpm installation for jboss

by Tom Baeyens (JIRA)

build jbpm installation for jboss --------------------------------- Key: JBPM-1963 URL: https://jira.jboss.org/jira/browse/JBPM-1963 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0.Beta1 ideally the result should be an installer which can install jbpm in jboss 5.0.latest and jboss 4.2.latest. also the choice of DB should be a choice just like in jbpm 3. the distribution will be a zip file containing this installer and the runtime installation directory structure. so the runtime installation directory should not be included in the installer. -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-1982) Provide a jbpm4 installer

by Heiko Braun (JIRA)

Provide a jbpm4 installer ------------------------- Key: JBPM-1982 URL: https://jira.jboss.org/jira/browse/JBPM-1982 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Installer Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0 Alpha2 -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-2009) Supply a jPDL 4 schema

by Heiko Braun (JIRA)

Supply a jPDL 4 schema ---------------------- Key: JBPM-2009 URL: https://jira.jboss.org/jira/browse/JBPM-2009 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Reporter: Heiko Braun Assignee: Tom Baeyens Fix For: jBPM 4.0.0.Beta2 -- 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, 10 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2009