May 2008 - jbpm-issues - Jboss List Archives

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

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-165?page=all ] Koen Aers updated JBPM-165: --------------------------- Fix Version/s: jBPM jPDL 3.2.4 (was: jBPM jPDL 3.2.3) > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: http://jira.jboss.com/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.4 > > > 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-807) Allow assignment of jBPM variables via EL evaluation

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-807?page=all ] Koen Aers updated JBPM-807: --------------------------- Fix Version/s: jBPM jPDL 3.2.4 (was: jBPM jPDL 3.2.3) > Allow assignment of jBPM variables via EL evaluation > ---------------------------------------------------- > > Key: JBPM-807 > URL: http://jira.jboss.com/jira/browse/JBPM-807 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Gavin King > Assigned To: Tom Baeyens > Priority: Critical > Fix For: jBPM jPDL 3.2.4 > > > A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value. > What I want is to be able to say: > <assign variable="orderId" value="#{order.id}"/> > when a transition occurs. -- 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

15 years, 12 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-836) "ejb local timer lookup problem" in EjbSchedulerService.java

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-836?page=comments#action_12412267 ] Alejandro Guizar commented on JBPM-836: --------------------------------------- The EjbSchedulerService looks up an entry in the java:comp/env context which is only available inside the command service bean. Any code running outside that bean will not be able to retrieve the timer bean unless the local-jndi-name above is used. The problem is, changing the EjbSchedulerService to use the local-jndi-name would render it nonportable. A J2EE component can only reliably access the java:comp/env context. Hence, a custom enterprise component that calls jBPM APIs and hits the scheduler service needs to declare an ejb reference in ejb-jar.xml like this: <session> <ejb-name>MySessionBean</ejb-name> <ejb-local-ref> <ejb-ref-name>ejb/LocalTimerServiceBean</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <local-home>org.jbpm.scheduler.ejbtimer.LocalTimerServiceHome</local-home> <local>org.jbpm.scheduler.ejbtimer.LocalTimerService</local> </ejb-local-ref> </session> The custom component's jboss.xml descriptor links the above ejb reference to the LocalTimerServiceHome bound to the local-jndi-name specified in jbpm-enterprise.jar!/META-INF/jboss.xml. <session> <ejb-name>MySessionBean</ejb-name> <ejb-local-ref> <ejb-ref-name>ejb/LocalTimerServiceBean</ejb-ref-name> <local-jndi-name>TimerServiceBean</local-jndi-name> </ejb-local-ref> </session> Note that "global" JNDI names are confined to the JBoss-specific descriptors. Nowhere in the Java code or the standard descriptors does a global JNDI name appear. > "ejb local timer lookup problem" in EjbSchedulerService.java > ------------------------------------------------------------ > > Key: JBPM-836 > URL: http://jira.jboss.com/jira/browse/JBPM-836 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2 beta 2 > Environment: cvs trunk build, jboss AS 4.0.5GA, ejb3, jms messaging > deploying jbpm-enterprise.ear > Reporter: Chris Russell > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.3 > > > After deploying the jbpm-enterprise.ear to a jboss 4.0.5ga server getting an exception when trying to signal a transition to the end state. > ===EXCEPTION SEEN=== > 13:04:56,785 ERROR [ProcessInstanceBean$SignalTokenListener] Action threw an exception: ejb local timer lookup problem > JNDI name lookup in EjbSchedulerService using incorrect name/and or the TimerServiceBean not declared in > jboss.xml. > ===CODE FIXES FOR EXCEPTION== > RCS file: /cvsroot/jbpm/jbpm.3/enterprise/src/main/java/org/jbpm/scheduler/ejbtimer/EjbSchedulerService.java,v > retrieving revision 1.1 > diff -r1.1 EjbSchedulerService.java > 31c31,36 > < LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("java:comp/env/ejb/LocalTimerServiceBean"); > --- > > > > > > //RSC wrong name used > > //LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("java:comp/env/ejb/LocalTimerServiceBean"); > > //See also change to jboss.xml to include TimerServiceBean or this fix wont work either. > > LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("TimerServiceBean"); > RCS file: /cvsroot/jbpm/jbpm.3/enterprise/src/main/resources/jar/META-INF/jboss.xml,v > retrieving revision 1.2 > diff -r1.2 jboss.xml > 12a13,20 > >  > > <session> > > <ejb-name>TimerServiceBean</ejb-name> > > <jndi-name>ejb/TimerServiceBean</jndi-name> > > <local-jndi-name>TimerServiceBean</local-jndi-name> > > </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
0
0 / 0

[JBoss JIRA] Commented: (JBPM-569) improve EL expression examples in the user guide

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-569?page=comments#action_12412262 ] Ronald van Kuijk commented on JBPM-569: --------------------------------------- I miss the relation, but it is late (0.44) > improve EL expression examples in the user guide > ------------------------------------------------ > > Key: JBPM-569 > URL: http://jira.jboss.com/jira/browse/JBPM-569 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Ronald van Kuijk > Fix For: jBPM jPDL 3.2.3 > > -- 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
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1081) Simulation query with stddev not supported on HSQL

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1081?page=comments#action_12412255 ] Koen Aers commented on JBPM-1081: --------------------------------- Has this been solved Bernd? At least, I can't see it in the build that I am doing from HEAD. > Simulation query with stddev not supported on HSQL > -------------------------------------------------- > > Key: JBPM-1081 > URL: http://jira.jboss.com/jira/browse/JBPM-1081 > Project: JBoss jBPM > Issue Type: Bug > Components: Simulation > Affects Versions: jBPM jPDL 3.2.3 > Environment: N/A > Reporter: Ronald van Kuijk > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.3 > > > According to a user in the forum, stddev is not supported in the HSQLDialect on the hibernate version that comes with jBPM. I have not had the opportunity to verify this. -- 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
0
0 / 0

[JBoss JIRA] Commented: (JBPM-886) change ejb timers from SLSB to an entity bean approach

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-886?page=comments#action_12412248 ] Alejandro Guizar commented on JBPM-886: --------------------------------------- I'll add some more tests based on the pvm enterprise timer, which works under the same idea. > change ejb timers from SLSB to an entity bean approach > ------------------------------------------------------ > > Key: JBPM-886 > URL: http://jira.jboss.com/jira/browse/JBPM-886 > Project: JBoss jBPM > Issue Type: Feature Request > Reporter: Tom Baeyens > Assigned To: Alejandro Guizar > Priority: Critical > Fix For: jBPM jPDL 3.2.3 > > > the problem is that all the timers are put on a single slsb. so we have to loop through all the timers to cancel or find one. that is a bottleneck. > we need to change that approach to the use of entity beans. 1 entity bean per job. so that we can put queries for jobs and that way have a more efficient way of finding and cancelling ejb timers. -- 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
0
0 / 0

[JBoss JIRA] Assigned: (JBPM-886) change ejb timers from SLSB to an entity bean approach

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-886?page=all ] Alejandro Guizar reassigned JBPM-886: ------------------------------------- Assignee: Alejandro Guizar (was: Tom Baeyens) > change ejb timers from SLSB to an entity bean approach > ------------------------------------------------------ > > Key: JBPM-886 > URL: http://jira.jboss.com/jira/browse/JBPM-886 > Project: JBoss jBPM > Issue Type: Feature Request > Reporter: Tom Baeyens > Assigned To: Alejandro Guizar > Priority: Critical > Fix For: jBPM jPDL 3.2.3 > > > the problem is that all the timers are put on a single slsb. so we have to loop through all the timers to cancel or find one. that is a bottleneck. > we need to change that approach to the use of entity beans. 1 entity bean per job. so that we can put queries for jobs and that way have a more efficient way of finding and cancelling ejb timers. -- 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
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-400) failed to lazily initialize a collection of role: org.jbpm.taskmgmt.def.TaskController.variableAccesses

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-400?page=all ] Alejandro Guizar resolved JBPM-400. ----------------------------------- Resolution: Rejected Ignoring on request of the reporter. > failed to lazily initialize a collection of role: org.jbpm.taskmgmt.def.TaskController.variableAccesses > ------------------------------------------------------------------------------------------------------- > > Key: JBPM-400 > URL: http://jira.jboss.com/jira/browse/JBPM-400 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Environment: Windows XP > Reporter: Derek Cornelius > Assigned To: Tom Baeyens > > This exception occurs when JBPM tries to load an existing TaskController from the DB. > The variableAccesses variable is accesed directly at line 62 in TaskController.java instead of the getter method. Thus Hibernate cannot return the lazily loaded collection for the current session. When the old collection is returned, the error occurs when it is accessed. -- 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
0
0 / 0

[JBoss JIRA] Commented: (JBPM-569) improve EL expression examples in the user guide

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-569?page=comments#action_12411822 ] Koen Aers commented on JBPM-569: -------------------------------- Could this be the problem of the trailing blanks? > improve EL expression examples in the user guide > ------------------------------------------------ > > Key: JBPM-569 > URL: http://jira.jboss.com/jira/browse/JBPM-569 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Ronald van Kuijk > Fix For: jBPM jPDL 3.2.3 > > -- 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
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues May 2008