[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1288) evaluate the previous methods
[
https://jira.jboss.org/jira/browse/JBPM-1288?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1288:
-----------------------------------
I think the previous properties feel like a hack. Because it is actually the history
information of how you get to where you are that you need in the general case. It's
only because we have one special use case that only needs the last transition that we have
introduced it. So I would like them to see removed from the API.
They're used in iterations like in a while activity. For that use case, a system
variable that stores the current index could be used as well.
They're also used for joining, to see if an execution came in over each incoming
transition. But an alternative here is to compare the number of incoming transitions with
the number of executions positioned in the join node.
With these two replacements, i would think it is better to remove the previous
properties.
Guillaume will ask Miguel if the previous properties are really needed in XPDL or BPEL
evaluate the previous methods
-----------------------------
Key: JBPM-1288
URL: https://jira.jboss.org/jira/browse/JBPM-1288
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: PVM
Reporter: Tom Baeyens
this relates to
Execution.getPreviousNode()
Execution.getPreviousTransition()
Node.isPreviousNeeded()
Comment in Execution.java:
// TODO evaluate the previous methods
// these methods are kind of performance optimisations. a sequence and
// some other specific control flow implementations can be optimised if they
// have access to the previous node or transition.
// Those activities could also be implemented by letting the activities store
// the contextual information in process variables or some other execution
// context. But with the previous properties as done now, these control flow
// nodes can be implemented without storing an extra record. It's only a property
// that is only updated when the node configuration indicates that it's needed.
// (see also Node.isPreviousNeeded())
--
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