Thank you for the assistance.
In the expression below, jbpmDecideHasSupplierApprover is a Spring bean. We have integrated Spring with our JBPM inplementation.
<decision g="901,209,48,48" name="decision.supplierInitApprover">
<handler expr="#{jbpmDecideHasSupplierApprover}"/>
<transition g="-50,-18" name="result.approver" to="state.supplierInitApproval"/>
<transition g="30,-80" name="result.noApprover" to="state.memberReview">
</decision>
We had difficulty getting JBPM to see our entire Spring context. Our Spring configuration is broken into several files and for some reason JBPM will only see the configuration and the beans in the file that it was created or loaded in.
As a result, We made a small extension to the Juel Script Engine and the configuration in order to expose out entire Spring context. This all worked great until we upgraded.
<script-manager default-expression-language="juel" default-script-language="juel"
read-contexts="execution, environment, process-engine, spring, springSca" write-context="">
<script-language name="juel" factory="com.premierinc.sca.agreement.util.ScaJuelScriptEngineFactory" />
</script-manager>
Any help would be GREATLY appreciated! We could really use the new API features of 4.4 to be able to determine the transitions dynamically. However, if we have to give up Spring intergration then it is no longer viable.
Ken