[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2712) Ability to add timer to transitions in <custom> activity in the same way that they can be added to the <state> task.
[
https://jira.jboss.org/jira/browse/JBPM-2712?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2712:
----------------------------------------
Last comment by Martin should be ignored, this was due to a usererror.
'custom' element should be changed to:
<element name="custom">
<annotation>
<documentation>Uses a user defined, custom implementation of
ActivityBehaviour
</documentation>
</annotation>
<complexType>
<complexContent>
<extension base="tns:wireObjectType">
<sequence>
<element ref="tns:on" minOccurs="0"
maxOccurs="unbounded" />
<element name="transition" minOccurs="0"
maxOccurs="unbounded">
<complexType>
<complexContent>
<extension base="tns:transitionType">
<sequence>
<element ref="tns:timer" minOccurs="0" />
</sequence>
</extension>
</complexContent>
</complexType>
</element>
</sequence>
<attributeGroup ref="tns:activityAttributes" />
</extension>
</complexContent>
</complexType>
</element>
Ability to add timer to transitions in <custom> activity in the
same way that they can be added to the <state> task.
--------------------------------------------------------------------------------------------------------------------
Key: JBPM-2712
URL: https://jira.jboss.org/jira/browse/JBPM-2712
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Reporter: Martin Porter
It should be possible to add a <timer> as the child of the <transition>
element contained within a <custom> activity in the same manner that it is for
<state> activities. If a custom activity executes a waitForSignal() inside the
execute() element (as is the case in our use case) then we need to be able to put a
timeout on this activity such that if no signal is recieved within a specified period the
timeout will fire and action can be taken. This is possible in a <state> activity
but currently not in the custom activity. We tried to do this by changing our
<custom> with a <state> and this worked for the timeout but the signalling
then failed (see JIRA JBPM-2711) so currenty we can find no solution to this issue.
--
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