This post goes along with the .bpm archives feature talked about here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051925#...
When deploying a .bpm archive, you will also be able to include action, handler, and other
utility classes within this archive. You will also be able to classloader scope these
classes so that when the process instance is being executed on, it will run inside the
configured classloader.
How I/we will do this is still a mystery to me at the moment. At the Command Service
layer, this is pretty straight forward. Just have some association someplace with the
process definition and a classloader and push/pop the classloader when a message comes in.
Referencing the process definitions, instances, tasks, tokens, etc... from standard JBPM
APIs and being able to run with the correct classloader is a different problem and will
need to be thought out more.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051926#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...