My first impressions:
- the mbean is of type JbpmService
- it creates a JbpmConfiguration which it binds in the jndi tree
- in the webapp (jsf based) the JbpmBean plays an important role, especially
the method getJbpmContext()
So most likely it would be enough to do something like
JbpmContext jbpmContext =
JbpmConfiguration.getInstance().createJbpmContext();
And as far as I can tell, there is no difference between using jBPM from the
sar or embedded. It could be however that there are some changes in this area
(I know some things are goiong on to change from mbean deployed to jca)
Further I have not tried this yet (no time today) but asked Tom to give a short
comment on this.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942438#3942438
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942438
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
