[
http://jira.jboss.com/jira/browse/JBSEAM-1939?page=comments#action_12377878 ]
Matthew Lieder commented on JBSEAM-1939:
----------------------------------------
FYI, this is my current (ugly) work-around:
@Name("hacks")
@Scope(ScopeType.STATELESS)
public class Hacks {
/**
* This is used to work around the limitation in jPDL pageflows where only the first
<action> child of <page>
* is executed. Put this in the first action, and pass all the methods you want to
execute as arguments to this.
*/
public void multiMethods(Object ...objects) {}
}
<page name="page1" view-id="/page1.xhtml">
<action expression="#{hacks.multiMethods( someMethodThatIsExecuted(),
someMethodThatIsExecuted() ) } />
</page>
Only the first action is executed inside a page node in a jPDL
pageflow
-----------------------------------------------------------------------
Key: JBSEAM-1939
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1939
Project: JBoss Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.0.0.CR1
Environment: JRE 1.5, Tomcat 5.5.23
Reporter: Matthew Lieder
Multiple <action> elements are allowed as children of <page> and
<start-page> elements in a jPDL pageflow, but only the first <action> is
executed. Please fix it so that all <action> elements are executed (like they are
when children of <transition> elements).
Example:
<page name="page1" view-id="/page1.xhtml">
<action expression="#{someMethodThatIsExecuted} />
<action expression="#{someMethodThatIsNotExecuted} />
<transition name="save" to="terminate">
<action expression="#{someMethodThatIsExecuted} />
<action expression="#{someMethodThatIsExecuted} />
</transition>
</page>
--
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