JBpm Pageflow - Decision property lookup handling

[js8523]

Hi All

I am working of the current CVs as of today, and I am wondering whether what I have encountered is the desired behaviour:

I am using the jbpm pageflow, with a decision handler :

<decision name="DefineContracts" expression="#{createSiteWizard.defineContracts}">
 <transition name="yes" to="Contracts">
 <action expression="#{createSiteWizardContracts.create}" />
 </transition>
 <transition name="no" to="DefinePlots"/>
</decision>

when the el evaluates the expression it assumes defineContracts is a property in my Stateful Seam managed bean (it is actually just a method). I would imagine that we would like to use either a property or a method (as long as it returned a String) for a decision using the faces context varaiables (of which Seam is a sub class variable resolver).

Crazily enough I had this running a few days ago on CVS version of Seam, so imagine something has been clarified/changed recently that directly affects this?

Many thanks for your reply.

James

[gavin.king]

Yes, I changed to use a JSF value binding instead of a method binding, so that you can do stuff like:




Yes, I realize that "expression" is interpreted slightly differently depending upon whether it is on an action or on a decision. To be totally consistent with JSF it would be better to have but that is just too bizarre.