[
http://jira.jboss.com/jira/browse/JBSEAM-391?page=all ]
Gavin King closed JBSEAM-391.
-----------------------------
Resolution: Done
Fixed by splitting out <end-task/> from <end-conversation/>. Need a doco
update!
<end-conversation /> ends task
------------------------------
Key: JBSEAM-391
URL:
http://jira.jboss.com/jira/browse/JBSEAM-391
Project: JBoss Seam
Issue Type: Bug
Components: BPM
Affects Versions: 1.1.0.BETA2
Environment: CVS @ 13:50 -0000 2006/11/06
Reporter: Peter Muir
Assigned To: Gavin King
Fix For: 1.1.0.CR1
Attachments: pageflow-transition-endTask.patch, pageflow-transition.patch
The reference manual says 'Optionally, we can specify a transition name. In this
case, Seam will signal the end of the current task in the overarching business
process.' (4.2.5)
Whether or not you specify a transition on <end-conversation /> if a task instance
is active then it will be ended.
This is because in Page.java the execute method has
if ( transition == null )
{
task.end();
}
else
{
task.end(transition);
}
How about adding endTask="true|false" (default true) to end-conversation and
altering Page.java accordingly?
This functionality would be useful if you want to 'cancel' out of a pageflow and
returrn to the task at a later date.
--
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