i'm starting to see a problem here. please think along and give your opinion:
currently the webapp just uses creates jbpmContexts and performs operations on the
jbpmContext in the backing beans. there can only be 1 hibernate configuration that is
used in the webapp. so you need to do a non-CMT based configuration. in case users want
to use the enterprise beans, this would imply that we have to create 2 jbpm configurations
on jboss: one for the webapp (without CMT configurations) and one for the CMT enterprise
beans. hmmm let me know if you don't follow this then i'll try to explain in
different words.
could it be that we need to solve this by implementing the command based interface between
the web app and the jbpm command service ? that way, the command service implementation
can be the enterprise command service SLSB or in a plain web application packaging, the
command service bean could be a simple POJO based command service.
makes sense ?
i'll sleep on it. maybe that helps
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966732#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...