April 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1154) jBPM example "action" - wrong package name referenced in JUnit tests

by Len DiMaggio (JIRA)

jBPM example "action" - wrong package name referenced in JUnit tests -------------------------------------------------------------------- Key: JBPM-1154 URL: http://jira.jboss.com/jira/browse/JBPM-1154 Project: JBoss jBPM Issue Type: Bug Components: Training Affects Versions: jBPM jPDL 3.2.2 Reporter: Len DiMaggio Assigned To: Tom Baeyens Priority: Minor Project issue for http://jira.jboss.com/jira/browse/SOA-481 -- 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
2
0 / 0

[JBoss JIRA] Created: (JBPM-1084) NPE in VariableAccess with Oracle persistence

by Tom Baeyens (JIRA)

NPE in VariableAccess with Oracle persistence --------------------------------------------- Key: JBPM-1084 URL: http://jira.jboss.com/jira/browse/JBPM-1084 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Tom Baeyens Assigned To: Tom Baeyens Oracle treats empty strings as null values. So the Access component value object is removed after storage and retrieval fronm the db in case the Access value field is an empty string. As a solution, an empty string is replaced with a space in case an Access object is created with an empty string. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1165) Adding a JBPM DecisionHandler to a Decision node using JBPM API.

by sumudu prabhani (JIRA)

Adding a JBPM DecisionHandler to a Decision node using JBPM API. ---------------------------------------------------------------- Key: JBPM-1165 URL: http://jira.jboss.com/jira/browse/JBPM-1165 Project: JBoss jBPM Issue Type: Feature Request Affects Versions: jBPM 3.1.4 Environment: Windows Reporter: sumudu prabhani Assigned To: Tom Baeyens I want to know how to add a DecisionHandler to a Decision node programmatically.(Using JBPM API, not using XML). But still couldn't find a workaround to do this. Can you please help me? -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBPM-721) create ws call startProcess(String name)

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-721?page=comments#action_12410396 ] Ronald van Kuijk commented on JBPM-721: --------------------------------------- I still have to adapt my previous work (adding a 'module') to mach the changed build system. So that is the major part to do. That should be the main thing. I personally have no time for that atm, so have a look at e.g. the enterprise 'module' and make some build scripts. Take JDK 1.4 and 1.5 into accout etc.... > create ws call startProcess(String name) > ----------------------------------------- > > Key: JBPM-721 > URL: http://jira.jboss.com/jira/browse/JBPM-721 > Project: JBoss jBPM > Issue Type: Sub-task > Reporter: Ronald van Kuijk > Assigned To: Ronald van Kuijk > Priority: Minor > Fix For: jBPM 3.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, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-639) Support Forward Reference in process-state

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-639?page=all ] Ronald van Kuijk resolved JBPM-639. ----------------------------------- Fix Version/s: jBPM jPDL 3.2.3 Resolution: Out of Date already fixed in a previous release by using 'binding=late' > Support Forward Reference in process-state > ------------------------------------------ > > Key: JBPM-639 > URL: http://jira.jboss.com/jira/browse/JBPM-639 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1 > Reporter: Armin Haaf > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.3 > > > It is not possible to have a forward reference to a yet unknown process definition: > <process-definition name='hello world'> > <start-state name='start'> > <transition to='s' /> > </start-state> > <process-state name='st'> > <sub-process name='do something'/> > <transition to='end' /> > </process-state> > <end-state name='end' /> > </process-definition>" > where "do something" is deployed later. > This is a problem if process "A" creates a subprocess "B", which creates a subprocess "A". -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-721) create ws call startProcess(String name)

by Mauricio Salatino (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-721?page=comments#action_12409335 ] Mauricio Salatino commented on JBPM-721: ---------------------------------------- Can i contribute with this? i want to test and create new webservices functionallity.. could you recommend me something that is missing right now? > create ws call startProcess(String name) > ----------------------------------------- > > Key: JBPM-721 > URL: http://jira.jboss.com/jira/browse/JBPM-721 > Project: JBoss jBPM > Issue Type: Sub-task > Reporter: Ronald van Kuijk > Assigned To: Ronald van Kuijk > Priority: Minor > Fix For: jBPM 3.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, 8 months

1
0
0 / 0

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

by Luxitano Daniel (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1024?page=comments#action_12408885 ] Luxitano Daniel commented on JBPM-1024: --------------------------------------- I have exactly the same problem with the jbpm-starters-kit-3.1.4. I think it's a problem of classloader but I don't know where the ProcessClassLoader is defined. Here is the full stack trace : by: org.jbpm.JbpmException: couldn't deserialize object at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.revert(SerializableToByteArrayConverter.java:66) at org.jbpm.context.exe.VariableInstance.getValue(VariableInstance.java:146) at org.jbpm.context.exe.VariableContainer.getVariableLocally(VariableContainer.java:129) at org.jbpm.context.exe.VariableContainer.getVariable(VariableContainer.java:29) at org.jbpm.context.exe.ContextInstance.getVariable(ContextInstance.java:133) at org.jbpm.context.exe.ContextInstance.getVariable(ContextInstance.java:121) at com.sample.action.ItemsInStock.execute(ItemsInStock.java:26) at org.jbpm.graph.def.Action.execute(Action.java:123) at org.jbpm.graph.def.Action$$FastClassByCGLIB$$7876e90e.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:136) at org.jbpm.graph.def.Action$$EnhancerByCGLIB$$ff3b8cb.execute(<generated>) at org.jbpm.graph.def.Node.execute(Node.java:328) ... 59 more by: java.lang.ClassNotFoundException: No ClassLoaders found for: data.TestSerVar at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:198) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:475) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:377) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:574) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1538) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339) at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.revert(SerializableToByteArrayConverter.java:64) ... 71 more and the variable class is serializable : package data; import java.io.Serializable; public class TestSerVar implements Serializable{ /** * */ private static final long serialVersionUID = 1L; private int idBuyer; public TestSerVar(int idB){ setIdBuyer(idB); } private void setIdBuyer(int idB){ this.idBuyer = idB; } public int getIdBuyer(){ return idBuyer; } } > 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 > Reporter: thilker > Assigned To: Tom Baeyens > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1060) Add EL support for Timer properties

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1060?page=comments#action_12407908 ] Ronald van Kuijk commented on JBPM-1060: ---------------------------------------- afaik, I already added this feature reqeust in CVS, can you verify? > Add EL support for Timer properties > ----------------------------------- > > Key: JBPM-1060 > URL: http://jira.jboss.com/jira/browse/JBPM-1060 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.2 > Reporter: Fabien Coppens > Assigned To: Tom Baeyens > > It would be very useful to be able to obtain Timer properties (such as duedate) from implicit variables such as ContextInstance. -- 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, 8 months

1
0
0 / 0

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

by JeanDenis Bertron (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1008?page=comments#action_12407421 ] JeanDenis Bertron commented on JBPM-1008: ----------------------------------------- I don't think Hibernate's lazy loading is an advantage at all. Sure there is the performance/resource issue. Maybe I don't understand the idea but I though lazy loading implied some kind of transparency from the point of view of the client. But I have yet to see how I can use the objects that were incompletely loaded by the lazy mechanism without having to call hibernate.initialize() repeatedly. For instance, if you want to navigate from a node to its tasks to the controllers and their variables you have to call Hibernate.initialize on every single one. It's the opposite of transparency and the code would be better off with a true API as in : context.getTasksForNode(..) context.getControllersforTask() context.getVariablesForController(). As for the Hibernate collections I agree with Adrian above. And it's a shame the client has to include Hibernate as a dependency without being able to use them. Even then, the functionality is severely restricted because you can't navigate the object tree properly for fear of causing a hibernate aneurysm. For instance, why can't Node.getTasks() handle the work of figuring out if the data is there and do the work to get it appropriately ? I mean, when the node was built, the remote interface or local context is available, and could be used again either to tell Hibernate to fetch the stuff or to manufacture a Command for the remote interface. J.D. > 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.3 > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-642) Signaling RootToken on Fork Node

by JeanDenis Bertron (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-642?page=comments#action_12407204 ] JeanDenis Bertron commented on JBPM-642: ---------------------------------------- Wow, I'm surprised that almost a year has passed and nothing has been done about this. If Forks and Joins don't work as expected -especially according to the documentation - then it's pretty frustrating. > Signaling RootToken on Fork Node > --------------------------------- > > Key: JBPM-642 > URL: http://jira.jboss.com/jira/browse/JBPM-642 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Enric Cecilla > Assigned To: Tom Baeyens > > Giving the following processdefinition: > *start->fork->a->join->end > ->b ^ > When RootToken is on Fork node trying to signal again the RootToken actually moves the token to one branch state, then RootToken can be signalled til it is on the Join node. At that moment it can be signalled again and it leaves the Join node. > pi.signal(); > assertEquals( "fork", pi.getRootToken().getNode().getName() ); //true > pi.signal(); > assertEquals( "b", pi.getRootToken().getNode().getName() ); //true > pi.signal(); > assertEquals( "join", pi.getRootToken().getNode().getName() ); //true > Does it makes any sense being able to signal a RootToken on Fork node which has children on every branch? From my point of view signalling on that condition should throw and Exception. Only child tokens should be allowed to signal since "real" tasks are on child tokens -- 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, 8 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 April 2008