What is also suprising is if I inject Seam component "processInstance" into "workEffortRecipient", this var is also null. Most probably this happens because jBPM writes its process instance variables into the database within a transaction of a separate hibernate session. But, shouldn't Seam hold outjected variables of scope=BUSINESS_PROCESS in its context (for later injections) for at least until jBPM has committed its transaction? If not, it would never be possible to define one or more actions in jPDL to be correctly be executed until the first wait-state occurred... And this would mean, that you can't use fine-grained Seam components in conjunction with jBPM workflows. Manuel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028974#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...