May 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2759) Make duedate accept subtractions with EL and business duration

by Ronald van Kuijk (JIRA)

Make duedate accept subtractions with EL and business duration --------------------------------------------------------------- Key: JBPM-2759 URL: https://jira.jboss.org/jira/browse/JBPM-2759 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0, jBPM 4.1, jBPM 4.2, jBPM 4.3 Reporter: Ronald van Kuijk Priority: Minor Subtraction in combination with EL is not implemented. See JBPM-2745 (not was it in jBPM 3: JBPM-1776 so it is no regression) -- 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

14 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBPM-2813) Do not throw exception from BusinessCalendar when calculated end date ends up in the past

by Per Christian Henden (JIRA)

Do not throw exception from BusinessCalendar when calculated end date ends up in the past ----------------------------------------------------------------------------------------- Key: JBPM-2813 URL: https://jira.jboss.org/jira/browse/JBPM-2813 Project: jBPM Issue Type: Patch Security Level: Public (Everyone can see) Reporter: Per Christian Henden Fix For: jBPM 4.x The case where the subtract method is called with a duedate expression and reference date that resolves to a date in the past is handled by throwing a JbpmException ("duedate <date> ends in the past"). While this may sound like a good decision in theory, it is problematic in practice. As a user of the API it means I have two choices when calling the subtract method. I must either -resolve the calcuation myself- before calling the method, to avoid the exception, or I must catch the -generic- JbpmException and decide on a duedate myself not knowing what went wrong. When someone requests a date that is in the past in this way there's basically three options: 1) Let them have it. - This seems like a silly solution to me, duedates in the past doesn't make sense. 2) Throw an error. - In this case a specific exception should be thrown so that the user of the API can know why he got an exception. An alternative to today's solution is to throw a less generic exception, maybe 'DueDateIsInThePastException' or IllegalArgumentException. 3) Return the current date, i.e. return Clock.getTime(). - Optionally a warning that the date was overriden to not be in the past can be logged, but this seems unecessary to me. Attached patch implements alternative #3 (against trunk/revision 6208), which I believe is the best choice. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2585) review / cleanup ExpressionEvaluatorDescriptor

by Tom Baeyens (JIRA)

review / cleanup ExpressionEvaluatorDescriptor ---------------------------------------------- Key: JBPM-2585 URL: https://jira.jboss.org/jira/browse/JBPM-2585 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.2 see if it can be removed or make a jira issue to remove it in one of the next versions -- 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

14 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-2854) If exception handlers are defined in multiple nodes, only the first one is triggered during one execution

by Toshiya Kobayashi (JIRA)

If exception handlers are defined in multiple nodes, only the first one is triggered during one execution --------------------------------------------------------------------------------------------------------- Key: JBPM-2854 URL: https://jira.jboss.org/jira/browse/JBPM-2854 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8 Reporter: Toshiya Kobayashi If you run a process definition below with ExceptionActionHandler which throws IllegalArgumentException, the first exception will be handled by the first exception handler and the second exception won't be handled --- will be thrown as a DelegationException to the client. This behavior was introduced by JBPM-1887 to avoid infinite loop. But ExecutionContext.exception can be cleared after handling the exception. Then avoiding loop and using multiple exception handlers will be achieved at a time. ============== <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="sample"> <start-state name="start-state1"> <transition to="node1"></transition> </start-state> <node name="node1"> <event type="node-enter"> <script> System.out.println("node1 called."); </script> <action class="com.test.action.ExceptionActionHandler"></action> </event> <exception-handler exception-class="java.lang.IllegalArgumentException"> <script> System.out.println("node1 Exception Handler OK."); </script> </exception-handler> <transition to="node2"></transition> </node> <node name="node2"> <event type="node-enter"> <script> System.out.println("node2 called."); </script> <action class="com.test.action.ExceptionActionHandler"></action> </event> <exception-handler exception-class="java.lang.IllegalArgumentException"> <script> System.out.println("node2 Exception Handler OK."); </script> </exception-handler> <transition to="end-state1"></transition> </node> <end-state name="end-state1"></end-state> </process-definition> -- 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

14 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2753) Simplify map specification in jPDL for simple case

by M M (JIRA)

Simplify map specification in jPDL for simple case -------------------------------------------------- Key: JBPM-2753 URL: https://jira.jboss.org/jira/browse/JBPM-2753 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.2 Reporter: M M Allow simpler specification of maps in the case where both the key and value are strings, by allowing key and value to be specified as attributes of the <entry> element, instead of as child elements. This will greatly reduce the verbosity of the XML for this common case. The following <custom class="com.company.CustomActivity" name="some_step"> <property name="inputs"> <map> <entry> <key> <string value="input_file_a" /> </key> <value><string value="some_filename" /></value> </entry> <entry> <key> <string value="another_input" /> </key> <value><string value="1234" /></value> </entry> </map> </property> <transition to="next_thing"/> </custom> would become simpler, as <custom class="com.company.CustomActivity" name="some_step"> <property name="inputs"> <map> <entry key="input_file_a" value="some_filename" /> <entry key="another_input" value="1234" /> </map> </property> <transition to="next_thing"/> </custom> -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2815) Support suspend/resume/restart of process instances through the API

by C Nayak (JIRA)

Support suspend/resume/restart of process instances through the API ------------------------------------------------------------------- Key: JBPM-2815 URL: https://jira.jboss.org/jira/browse/JBPM-2815 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Environment: Linux Reporter: C Nayak Provide the ability to suspend and resume process instances. Suspend/Resume behavior would be similar to the process definition suspend. -- 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

14 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2818) Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition

by Toshiya Kobayashi (JIRA)

Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition ------------------------------------------------------------------------------------------------------- Key: JBPM-2818 URL: https://jira.jboss.org/jira/browse/JBPM-2818 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8 Reporter: Toshiya Kobayashi Leaving <node> in <super-state> throws org.jbpm.JbpmException: cannot leave Node(node2) without leaving transition when I execute process definition like: ================ <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="id41"> <start-state name="start"> <transition to="super-state1"></transition> </start-state> <super-state name="super-state1"> <transition to="end"></transition> <node name="node1"> <transition to="node2"></transition> </node> <node name="node2"> </node> </super-state> <end-state name="end"> </end-state> </process-definition> ================= Note: <node name="node2"> doesn't have its own transition. but I expect super-state's transition is available then. The process definition works if you test via ProcessDefinition.parseXmlResource(String xmlResource) without DB/Hibernate (like org.jbpm.graph.exe.SuperStateActionExecutionTest.testNestedSuperStateLeaveViaSuperStateTransition()). What's the difference? org.jbpm.graph.def.Node: ========= public Transition getDefaultLeavingTransition() { Transition defaultTransition = null; if (leavingTransitions != null) { // Select the first unconditional transition for (Iterator i = leavingTransitions.iterator(); i.hasNext();) { Transition auxTransition = (Transition) i.next(); if (auxTransition.getCondition() == null) { defaultTransition = auxTransition; break; } } } else if (superState != null) { defaultTransition = superState.getDefaultLeavingTransition(); } return defaultTransition; } ========= The logic of getDefaultLeavingTransition() depends on whether leavingTransitions is null or not. But in case that hibernate kicks lazy initialization, leavingTransitions will be a zero sized collection, not null. BTW, I think the concept that super-state's transition can be chosen from nodes inside is better to be documented. -- 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

14 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2810) Add API functions to query process definition details (defined tasks, name of nodes etc)

by Peter Horvath (JIRA)

Add API functions to query process definition details (defined tasks, name of nodes etc) ---------------------------------------------------------------------------------------- Key: JBPM-2810 URL: https://jira.jboss.org/jira/browse/JBPM-2810 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Peter Horvath It would be great if there were public API methods which provide access to the process definition - for example to retrieve the name of the tasks defined in a process definition. -- 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

14 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2788) jbpm.bpmn.cfg.xml file is missing in distibution .zip file

by Dawid Booyse (JIRA)

jbpm.bpmn.cfg.xml file is missing in distibution .zip file ---------------------------------------------------------- Key: JBPM-2788 URL: https://jira.jboss.org/jira/browse/JBPM-2788 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.x Environment: version 4.3 Reporter: Dawid Booyse The jbpm.bpmn.cfg.xml file is missing in the distribution .zip file. This results in that i can't enable bpmn 2.0 in the signavio web editor. The signavio web editor is stuck on version 1.2 of bpmn -- 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

14 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2792) Data manipulation with HQL / SQL nodes

by Peter Horvath (JIRA)

Data manipulation with HQL / SQL nodes -------------------------------------- Key: JBPM-2792 URL: https://jira.jboss.org/jira/browse/JBPM-2792 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.x Reporter: Peter Horvath Currently HQL / SQL nodes only allow you to run queries. It would be great if it was possible to run data manipulation operations (INSERT / UPDATE / DELETE) as well. It should be quite easy to implement this by adding a new possible flag to the hql / sql node and calling org.hibernate.Query.executeUpdate() from org.jbpm.jpdl.internal.activity.HqlActivity.perform(OpenExecution) method: if(isUpdate) { // isUpdate: this a new flag that indicates that this is a data manipulation operation // execute update and store the number of entities / rows affected (inserted, updated or deleted) by this operation into the result variable result = q.executeUpdate(); } else { if (isResultUnique) { result = q.uniqueResult(); } else { result = q.list(); } } -- 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

14 years, 4 months

2
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues May 2010