[JBoss JIRA] Created: (JBPM-1140) Empty <handler> element in <decision> cause org.jbpm.graph.def.DelegationException
by Rafa? ?ukowski (JIRA)
Empty <handler> element in <decision> cause org.jbpm.graph.def.DelegationException
----------------------------------------------------------------------------------
Key: JBPM-1140
URL: http://jira.jboss.com/jira/browse/JBPM-1140
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Reporter: Rafa? ?ukowski
Assigned To: Tom Baeyens
Priority: Trivial
That is my first issue, forgive me any mistakes and possible redundancy or duplication;)
Using graphical designer I've created process file with empty <handler> :
<decision name="decision1">
<handler></handler>
<transition to="optional" name="to optional"></transition><transition to="first" name="to optional"></transition>
</decision>
And this is not working (org.jbpm.graph.def.DelegationException). After deleting <handler></handler> process is running correctly.
Don't know if this is error in engine or in designer. Maby this kind of decision node is incorrect, and then designer should avoid this situation. My opinion is that engine should ignore empty handlers and go on without errors...
--
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
13 years, 6 months
[JBoss JIRA] Created: (JBPM-2696) Timers should be read after node-enter actions
by Bernd Ruecker (JIRA)
Timers should be read after node-enter actions
----------------------------------------------
Key: JBPM-2696
URL: https://jira.jboss.org/jira/browse/JBPM-2696
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.8
Reporter: Bernd Ruecker
Priority: Minor
Fix For: jBPM 3.2.x
When parsing the processdefinition, timers are read before all events are read.
This leads to "create-timer" actions being added to the node-enter events BEFORE your own actions. This doesn't make a lot of sense, normally you want your own actions being executed first and the timer created afterwards. From the runtime perspective, it doesn't make any difference (since the timer is started not before the transaciton commits), but with that behavior you could e.g. calculate due dates on the node-enter event (before the time is created).
This is located in the JpdlXmlReader, method "readNode", these two lines:
readNodeTimers(nodeElement, node);
readEvents(nodeElement, node);
See Forum on the discussion how to solve it.
--
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
13 years, 6 months
[JBoss JIRA] Created: (JBPM-2001) DbLoggingService -> Protected Session Rather than Package Private
by Brad Davis (JIRA)
DbLoggingService -> Protected Session Rather than Package Private
-----------------------------------------------------------------
Key: JBPM-2001
URL: https://jira.jboss.org/jira/browse/JBPM-2001
Project: JBoss jBPM
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.x
Reporter: Brad Davis
Priority: Minor
Fix For: jBPM 3.2.x
DBLoggingService should have a protected Hibernate session to allow extension. See patch below.
### Eclipse Workspace Patch 1.0
#P jbpm
Index: modules/core/src/main/java/org/jbpm/logging/db/DbLoggingService.java
===================================================================
--- modules/core/src/main/java/org/jbpm/logging/db/DbLoggingService.java (revision 3699)
+++ modules/core/src/main/java/org/jbpm/logging/db/DbLoggingService.java (working copy)
@@ -31,7 +31,7 @@
private static final long serialVersionUID = 1L;
- Session session = null;
+ protected Session session = null;
public DbLoggingService() {
JbpmContext currentJbpmContext = JbpmContext.getCurrentJbpmContext();
--
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
13 years, 6 months
[JBoss JIRA] Created: (JBPM-1395) verify jbpm/soa integration
by Tom Baeyens (JIRA)
verify jbpm/soa integration
---------------------------
Key: JBPM-1395
URL: https://jira.jboss.org/jira/browse/JBPM-1395
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jPDL 3
Reporter: Tom Baeyens
Fix For: jPDL 3.2.4
ESB people have already done some good work on trying to get jBPM integrated into ESB and the rest of the SOA platform. But this work should be verified from a jBPM perspective.
Mainly it should be verified if there is enough coverage of the different transaction scenarios. E.g. a rollback in case of multiple transactional resources.
More can be found in the related SOA issue description
--
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
13 years, 6 months