It seems that the jbpmConfiguration member variable is initalised lazily inside the org.jboss.seam.core.Jbpm class - which is good.
However the initialisation only occurs inside the installProcessDefinitions method, *if* there is a context parameter that specifies a process to deploy. This leaves the jbpmConfiguration member unitialized in other circumstances. My application (like the JBPM sample app) allows the user to upload process definitions at runtime and so I don't preload any particular definition. Therefore bad things happen when I try and use the jbpmContext component with it's unitialised jbpmConfiguration member variable. This problem could be fixed by moving the lazy intialization of the jbpmConfiguration to the getJbpmConfiguration method. Cheers J View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930658#3930658 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930658 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
