June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1188) remove rejected issues from 3.2.3 release

by Tom Baeyens (JIRA)

remove rejected issues from 3.2.3 release ----------------------------------------- Key: JBPM-1188 URL: http://jira.jboss.com/jira/browse/JBPM-1188 Project: JBoss jBPM Issue Type: Task Reporter: Tom Baeyens Assigned To: Tom Baeyens 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, 6 months

2
1
0 / 0

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

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-836?page=all ] Koen Aers updated JBPM-836: --------------------------- Fix Version/s: (was: jBPM jPDL 3.2.3) > "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: Alejandro Guizar > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1175) CLONE -Wrong transition taken after ending a task with the taskform button

by Martin Loiacono (JIRA)

CLONE -Wrong transition taken after ending a task with the taskform button -------------------------------------------------------------------------- Key: JBPM-1175 URL: http://jira.jboss.com/jira/browse/JBPM-1175 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2.1 Reporter: Martin Loiacono Assigned To: Tom Baeyens Priority: Critical Fix For: jBPM jPDL 3.2.2 This behavior can be reproduced with the default suite by following these steps on the deployed "websale" demo process: 1. Login: admin/admin 2. Click 'Processes' (upper navigation) 3. Process ID 1, websale, click: Examine 4. Left navigation, click: Start a new instance 5. Task 'Create new web sale order' is displayed, click 'Examine' 6. Form for web sale order vars displayed, fill out, click 'Evaluate' 7. Click: Tasks (upper navigation) 8. Task 'Evaluate web order', click Actions: 'Examine' 9. Form for web sale order with filled vars is displayed, click 'More Info Needed' 10. Inspect the process instance via the Instance Link/Process Image --> the token has incorrectly moved down the 'ok' transition -- 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
5
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

[JBoss JIRA] Created: (JBPM-1190) Allow only one action element in a node

by Koen Aers (JIRA)

Allow only one action element in a node --------------------------------------- Key: JBPM-1190 URL: http://jira.jboss.com/jira/browse/JBPM-1190 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM jPDL 3.2.3, jBPM 3.2.2 SOA 1 -- 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

1
1
0 / 0

[JBoss JIRA] Closed: (JBPM-751) unnecessary warning on valid process definition

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-751?page=all ] Koen Aers closed JBPM-751. -------------------------- Resolution: Done fixed > unnecessary warning on valid process definition > ----------------------------------------------- > > Key: JBPM-751 > URL: http://jira.jboss.com/jira/browse/JBPM-751 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2, jBPM 3.1.2, jBPM 3.1.3, jBPM 3.1.4, jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Alex Burgel > Assigned To: Koen Aers > Priority: Minor > Fix For: jBPM jPDL 3.2.3, jBPM 3.2.2 SOA 1 > > > i get this warning: > process xml warning: warning: no swimlane or assignment specified for task '<task xmlns="urn:jbpm.org:jpdl-3.1" name="schedule" blocking="false" signalling="true" priority="normal"/>' > it seems a bit odd to generate a warning on a valid process definition. > i think it should either be illegal to have a task without an assignment or swimlane, or there shouldn't be any warning at all (maybe lower the logging level to INFO). -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-1055) make org.jbpm.job.Timer's businessCalendar field lazy init

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1055?page=all ] Tom Baeyens closed JBPM-1055. ----------------------------- Resolution: Deferred will be fixed in jPDL 4 > make org.jbpm.job.Timer's businessCalendar field lazy init > ---------------------------------------------------------- > > Key: JBPM-1055 > URL: http://jira.jboss.com/jira/browse/JBPM-1055 > Project: JBoss jBPM > Issue Type: Feature Request > Components: BPEL > Affects Versions: jBPM jPDL 3.2.1 > Environment: jbpm 3.2.1+sun jdk1.5 > Reporter: yi gong > Assigned To: Tom Baeyens > > When create jbpm hibernate session factory, The timer class will initialize its static member "businessCalendar" , and BusinessCalendar will find "resource.business.calendar" from jbpm config. This will create a default jbpmContext immediately. > The setDefaultObjectFactory function will be nouse after these steps. > How about to make businessCalendar lazy init until its first use? -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1024) Serializable variables are not being deserialized when retrieved from process

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1024?page=all ] Alejandro Guizar resolved JBPM-1024. ------------------------------------ Resolution: Done removed ClassUtil and replaced the processInstance static variable with a ClassLoader member field in CustomLoaderObjectInputStream > Serializable variables are not being deserialized when retrieved from process > ----------------------------------------------------------------------------- > > Key: JBPM-1024 > URL: http://jira.jboss.com/jira/browse/JBPM-1024 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.4, jBPM jPDL 3.2.2 > Reporter: thilker > Assigned To: Alejandro Guizar > Fix For: jBPM jPDL 3.2.3 > > > Storing an serializable object in a process should write an "R" in the column "converter" in table JBPM_VARIABLEINSTANCE. > But the value of the field is "null". > The cause: > The converter ID is retrieved in class org.jbpm.db.hibernate.Converter at line 63. > For the case of the SerializableToByteArrayConverter the ID is "null". > Regards, > Thorsten -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-742) Reimplement JobExecutorServlet as a ServletContextListener

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-742?page=all ] Alejandro Guizar resolved JBPM-742. ----------------------------------- Resolution: Done User guide references to the job executor servlet were moved to the servlet context listener. I also updated a section of the asynchronous continuations chapter that explained how the job executor worked in terms of old stuff such as the context builder, the message instance and the job interceptor. > Reimplement JobExecutorServlet as a ServletContextListener > ---------------------------------------------------------- > > Key: JBPM-742 > URL: http://jira.jboss.com/jira/browse/JBPM-742 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2 alpha 2 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM jPDL 3.2.3 > > > ServletContextListeners are a viable alternative to servlets for management of the jBPM scheduler/command threads. From the Servlet 2.4 spec, section 10.2: > >>> > Servlet event listeners support event notifications for state changes in the ServletContext, HttpSession and ServletRequest objects. > Servlet context listeners are used to **manage resources** or state held at a JVM level for the application. > <<< > Their intent definitely seems to match our purposes. > Further below: > >>> > There may be multiple listener classes listening to each event type. > <<< > We could have separate listeners for the scheduler and command executor so that applications may remove either of them in case the related service is not used. > Section 10.2.2 provides an example. When the application starts up, the listener creates a connection to the database and stores it in the servlet context. Servlets access the connection from the context as needed. When the application shuts down, the listener closes the connection. > Our listener could start the thread and store it in the servlet context, then stop it using the mechanisms provided by JBPM-741. -- 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

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1024) Serializable variables are not being deserialized when retrieved from process

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1024?page=comments#action_12415731 ] Alejandro Guizar commented on JBPM-1024: ---------------------------------------- The test passes on HEAD, but the code does not work if more than one process instance tries to deserialize an object concurrently. org.jbpm.util.ClassUtil.processInstance is static, but making it a member field is not enough. This issue still needs some work. > Serializable variables are not being deserialized when retrieved from process > ----------------------------------------------------------------------------- > > Key: JBPM-1024 > URL: http://jira.jboss.com/jira/browse/JBPM-1024 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.4, jBPM jPDL 3.2.2 > Reporter: thilker > Assigned To: Alejandro Guizar > Fix For: jBPM jPDL 3.2.3 > > > Storing an serializable object in a process should write an "R" in the column "converter" in table JBPM_VARIABLEINSTANCE. > But the value of the field is "null". > The cause: > The converter ID is retrieved in class org.jbpm.db.hibernate.Converter at line 63. > For the case of the SerializableToByteArrayConverter the ID is "null". > Regards, > Thorsten -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2008