JBPM Timer + Seam 2.1.0 not accessing instance variables

[xnejp03.pnejedly.ondemand.co.uk]

Hello,

we have a multi-module (many wars) application using Seam + JBPM. JbpmConfiguration is in its separate sar file exposing the config in JNDI and all the modules' components.xml point their jbpm components to it. We managed to make most of the things work, but now we're facing a problem of Timer-created task not being able to access instance variables. Jpdl is following:

<state name="Wait for expected delivery date">
          <timer name="Expected Delivery Date missed" duedate="#{expectedDeliveryDate}" transition="late delivery">               
          </timer>
          <transition to="Call Supplier" name="late delivery"></transition>
</state>

<task-node name="Call Supplier">
     <task name="Call Supplier" priority="high">
          <description>
                    Call Supplier #{supplierName} re: C.O. #{contentOrderId}, Title #{titleId}, #{titleName}
          </description>
          <assignment pooled-actors="Traffic"></assignment>
     </task>
</task-node>

Basically the timer (after it expires) creates a Task which in its description uses EL to access the variables. After some debugging I found out the SeamELResolver cannot process this EL since applicationContext is not active.

Is there a way how to configure timers to run inside the Seam's application Context? Or skip Seam's EL resolver altogether for certain cases?

Thanks,

Petr

[xnejp03.pnejedly.ondemand.co.uk]

Anyone guys? Is it possible to invoke the JbpmJobLauncher in Seam context?

[xnejp03.pnejedly.ondemand.co.uk]

Anyone guys? Is it possible to invoke the JbpmJobLauncher in Seam context?

I mean JobExecutorLauncher

[mstruk.strukelj.parsek.net]

You can try this little hack that I'm using: JBSEAM-3837

[xnejp03.pnejedly.ondemand.co.uk]

Dude, this is it. I was trying to do something similar in the meantime, but your actually works :-)

Thanks a lot.

[mstruk.strukelj.parsek.net]

Dude, this is it. I was trying to do something similar in the meantime, but your actually works :-)

Good to hear :)

[kukeltje.ronald.jbpm.org]

Marko,

I tried doing a diff to the current jBPM source, but it yielded to many differences. Some changes are just cosmetic I think, some are more fundamental. Can't you make a version where jBPM the jBPM source is extended? And describe which changes you made for cosmetic reasons and why? Maybe I can get some changes into jBPM and a clean version that extends the jbpm one, will probably be more easily incorporated into Seam.

[mstruk.strukelj.parsek.net]

I tried doing a diff to the current jBPM source, but it yielded to many differences.

This hack is made off of JBPM 3.2.2 which is clearly mentioned in JIRA post, and in the sources.

Can't you make a version where jBPM the jBPM source is extended?

No. The essence of this hack is to rip apart the existing servlet and refactor it into a working seam component. Apart from this refactoring the essence of the hack are Lifecycle calls and transaction demarcation calls.

And describe which changes you made for cosmetic reasons and why?

There are no cosmetic changes.

Maybe I can get some changes into jBPM and a clean version that extends the jbpm one, will probably be more easily incorporated into Seam.

Thomas is working on a proper up-to-date solution to this issue. I don't see much sense in having 2 mechanisms for the same thing. I suggest you just wait for Thomas to finish up :)

- marko