Thanks for responding. The thing is that without some context it is difficult for us to differentiate between beginners and realy lazy people ;-) Therefor my suggestion to give som context.
Using the SAR is not because of the j2ee specs, it is more to have a single jBPM 'instance' that can be accessed from different applications. Embedding it is also possible, but then there can be db conflicts etc if used with the same database. You'd have to configure separate db's and jbpm configs then for multiple instances Threads are not 'forbidden' from servlets afaik, as long as you use it for things like quartz or our scheduler does. You should not create threads for each request that comes in etc. About the not writing to disk, I've never heard of that, but it is true that writing to disk cannot participate in a transaction, so if you need transacted persistence it is a no-no View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942444#3942444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942444 ------------------------------------------------------- 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
