[
https://jira.jboss.org/jira/browse/JBPM-1288?page=com.atlassian.jira.plug...
]
Tom Baeyens resolved JBPM-1288.
-------------------------------
Fix Version/s: jBPM 4.0.CR1
(was: jBPM 4.0)
Resolution: Done
those methods have been removed
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)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Priority: Minor
Fix For: jBPM 4.0.CR1
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