[
https://jira.jboss.org/browse/JBPM-1140?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar commented on JBPM-1140:
----------------------------------------
An empty handler element is incorrect. Its presence indicates an intention to invoke a
custom decision handler. It is unfeasible to require the designer to produce only valid
definitions, especially since it allows manual edition. Validation is the responsibility
of JpdlXmlReader and friends. Delegation.read() emits a warning if the /class/ attribute
is absent.
This warning should be escalated to an error, to prevent process deployment. Likewise, the
/class/ attribute of the /delegation/ complex type should be required.
Empty <handler> element in <decision> cause
org.jbpm.graph.def.DelegationException
----------------------------------------------------------------------------------
Key: JBPM-1140
URL:
https://jira.jboss.org/browse/JBPM-1140
Project: jBPM
Issue Type: Bug
Components: Runtime Engine
Affects Versions: jBPM 3.2.2
Reporter: Rafa? ?ukowski
Priority: Trivial
Fix For: jBPM 3.2.x
Original Estimate: 1 hour
Remaining Estimate: 1 hour
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.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira