May 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBPM-470) JBPM 3.0.2 and Hibernate 3.1 Error

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-470?page=all ] Ronald van Kuijk closed JBPM-470. --------------------------------- Resolution: Out of Date 3.0 will not receive fixes anymore > JBPM 3.0.2 and Hibernate 3.1 Error > ---------------------------------- > > Key: JBPM-470 > URL: http://jira.jboss.com/jira/browse/JBPM-470 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.2 > Environment: Windows XP Professional. Java JDK 1.5. MySql 5.0.15 > Reporter: Luke Mauldin > Assigned To: Tom Baeyens > > The below code cancels a timer after a task is completed: > JbpmSession jbpmSession = JBPMUtil.getJbpmSessionFactory().openJbpmSession(); > SchedulerInstance.CancelledTimer cancelledTimer = new SchedulerInstance.CancelledTimer("remind",executionContext.getToken()); > SchedulerSession schedulerSession = jbpmSession.getSchedulerSession(); > schedulerSession.cancelTimers(cancelledTimer); > executionContext.getToken().signal(); > jbpmSession.close(); > When run with Hibernate 3.0.5, the code runs fine. When run with Hibernate 3.1, there is an exception: > java.sql.SQLException: Unknown column 'token' in 'where clause'. > The sql query generated has a where clause of > "where name_ = ? and token = ?". Token is defined as token_ in the database thus the sql query cannot be executed. > The relevant portion of the Timer.hbm.xml is: > <property name="name" column="NAME_" /> > <many-to-one name="token" > column="TOKEN_" > foreign-key="FK_TIMER_TOKEN"/> > The Timer.hbm.xml looks fine to me. If this is not a JBPM bug/error I will post it to the Hibernate issue tracking 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-718) Add a webservice frontend to jBPM

by Mauricio Salatino (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-718?page=comments#action_12412663 ] Mauricio Salatino commented on JBPM-718: ---------------------------------------- This issue still active? Can i help you with something.. I am very interested in this.. but i do not know the state of this issue.. > Add a webservice frontend to jBPM > --------------------------------- > > Key: JBPM-718 > URL: http://jira.jboss.com/jira/browse/JBPM-718 > Project: JBoss jBPM > Issue Type: Feature Request > Environment: n/a > Reporter: Ronald van Kuijk > Assigned To: Ronald van Kuijk > Priority: Minor > Fix For: jBPM 3.3 > > > A webservice frontend is an interesting feature. A schema has to be designed, ws toolkit choosen (jbossws 1.0.2GA?) subdir created in the build, ant files etc... etc...etc... > Subtasks will be created for this. Anyone to jump in, feel free -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-675) Able to kill and suspend a process or token that has ended

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-675?page=all ] Koen Aers updated JBPM-675: --------------------------- Fix Version/s: jBPM 3.1.5 (was: jBPM jPDL 3.2.3) > Able to kill and suspend a process or token that has ended > ---------------------------------------------------------- > > Key: JBPM-675 > URL: http://jira.jboss.com/jira/browse/JBPM-675 > Project: JBoss jBPM > Issue Type: Patch > Components: Core Engine > Affects Versions: jBPM 3.1.1 > Environment: Mac OS X 10.4.6 Java 1.4.2_09 > Reporter: michaelklem > Assigned To: Tom Baeyens > Priority: Trivial > Fix For: jBPM 3.1.5 > > > When a process instance or token has ended, I can still call the suspend, resume and kill APIs on that process instance or token without an exception being thrown. IMO an exception should be thrown to indicate that these APIs are used in an illegal state. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1008) ejb deployment : avoid ClassNotFoundException on client side after unmarshalling

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1008?page=all ] Koen Aers updated JBPM-1008: ---------------------------- Fix Version/s: jBPM jPDL 3.2.4 (was: jBPM jPDL 3.2.3) > ejb deployment : avoid ClassNotFoundException on client side after unmarshalling > --------------------------------------------------------------------------------- > > Key: JBPM-1008 > URL: http://jira.jboss.com/jira/browse/JBPM-1008 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM jPDL 3.2.1 > Environment: enterprise jBPM > Reporter: Adrian Dimulescu > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.4 > > > Two aspects in this jira : 1: hide hibernate-specific exceptions; 2: hide hibernate-specific datatypes. > 1. The EJB client only depends on the jBPM jar (for the various Command implementations) and on the JBoss client jar. If a Hibernate exception occurs, it is wrapped by a JBPMException and rethrown. When deserialiezed on the client side (which does not have a Hibernate dependency), a ClassNotFoundException occurs. > I think the CommandServiceBean should not wrap internal implementation-specific exceptions; it should instead simply copy the stack trace and throw a new implementation-independent exception which contains the exception trace without containing the causes themselves. That typically avoids ClassNotFoundExceptions without losing exception history. > 2. The second problem is that hibernate-specific collections get serialized over the wire, here is the description of the problem : > I use the GetProcessInstancesCommand in order to experiment with querying the remote ejb. This command returns a list with ProcessInstances. A ProcessInstance is read by Hibernate from the database. As Hibernate uses specific lazy-loading-aware implementations for collections -- the ProcessInstance.instances attribute, which is declared of type java.util.Map, is actually implemented by org.hibernate.collections.PersistentMap. > Which generates class loading exception while deserializing to hibernate-unaware ejb clients. > The solution would then be for the Command implementations to return clean JDK collections, by replacing Hibernate collection with JDK standard ones. Note that IIUC only the collections must be replaced, not the collection contents too, so the "cleaning" operation should not be that expensive. Cleaning should be only done in the SLSB remote call use case -- because in-JVM callers may want to benefit lazy-loading. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-835) create strategy for dealing with example dependencies

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-835?page=all ] Koen Aers updated JBPM-835: --------------------------- Fix Version/s: jBPM jPDL 3.2.4 (was: jBPM jPDL 3.2.3) > create strategy for dealing with example dependencies > ----------------------------------------------------- > > Key: JBPM-835 > URL: http://jira.jboss.com/jira/browse/JBPM-835 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.4 > > > When I created a project in Eclipse with jbpm-jpdl-3.2.Beta2 as the source there was a number of compilation issues. These I could resolve as follows: > 1) jms example - remove or comment out the offending code. This example uses APIs that do not exist in the product. > 2) org.apache.tools.ant.BuildException in src/identity/LoadIdentitiesTask required ant.jar to be added to lib > 3) my rules examples require drools-compiler-3.0.5 and drools-core-3.0.5 to be added to lib > 4) org.jbpm.jcr.jackrabbit.JackrabbitJcrServiceFactory requires jackrabbit-core-1.0.1 to be added to lib -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1009) Assign other actors/groups to start-state-Tasks as the initiator

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1009?page=all ] Koen Aers updated JBPM-1009: ---------------------------- Fix Version/s: jBPM jPDL 3.2.4 (was: jBPM jPDL 3.2.3) Affects Version/s: jBPM jPDL 3.2.3 (was: jBPM jPDL 3.2) (was: jBPM jPDL 3.2.1) (was: jBPM jPDL 3.2.2) > Assign other actors/groups to start-state-Tasks as the initiator > ---------------------------------------------------------------- > > Key: JBPM-1009 > URL: http://jira.jboss.com/jira/browse/JBPM-1009 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.3 > Reporter: Andreas Schienagel > Assigned To: Tom Baeyens > Priority: Minor > Fix For: jBPM jPDL 3.2.4 > > > Like descriped in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112543 > It should be possible to assign other actors/groups to start-state-Tasks as the initiator in the usual way with > a swimmlane assignment. -- 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, 7 months

1
0
0 / 0

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

by Koen Aers (JIRA)

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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-787) centralize cache configurations

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-787?page=all ] Koen Aers closed JBPM-787. -------------------------- Resolution: Done > centralize cache configurations > ------------------------------- > > Key: JBPM-787 > URL: http://jira.jboss.com/jira/browse/JBPM-787 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.3 > > Attachments: hibernate.cfg.xml, jbpm.3-jpdl-hbm-cluster-patch.zip, jbpm.3-jpdl_3_2_2-hbm-cluster.patch.zip, jpwh-replicated-cache-excerpt.pdf > > > for easier update of the cache configurations. see attachment -- 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, 7 months

1
0
0 / 0

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

by Koen Aers (JIRA)

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

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-961) Save not required on jbpmContext operations

by joy wind (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-961?page=comments#action_12412566 ] joy wind commented on JBPM-961: ------------------------------- Yes , in jbpm3.2.2, It's seemed no need to call jbpmContext.save(aProcessInstance). The jbpmContext.close() method will save the process instance automaticly. Am I wrong ? how can I close the jbpmContext but not save the process instance ? > Save not required on jbpmContext operations > ------------------------------------------- > > Key: JBPM-961 > URL: http://jira.jboss.com/jira/browse/JBPM-961 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2 > Reporter: Jeff DeLong > Assigned To: Tom Baeyens > Priority: Minor > > Save (or ForUpdate methods) do not appear to be required on jbpmContext operations. > In the javadocs for JbpmContext it says > ...do your process operations... > // in case you update a process object that was not fetched > // with a .. ForUpdate method, you have to save it > jbpmContext.save(processInstance); > ... > "All of the ...ForUpdate(...) methods will automatically save the loaded object at jbpmContext.close(); > I have verified through JUnit tests that indeed saving of ProcessInstance and TaskInstance is not required, the state will still be persisted. -- 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, 7 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 May 2008