This is probably a lib conflict. We will be resolving this shortly. If you can't wait, you can try to take the hibernate and commons libs from the jboss 3.2.6 (or higher) and overwrite the corresponding libs in the jbpm distribution. then perform a clean build.
these issues with the ejb-wrapper should not be linked to the overall engine stability. focus has been on the core engine. the ejb wrappers were only included to show that jbpm was deployable on a clustered jboss. in the future, jbpm will remain deployable outside of jboss, but of course, we will work hard on smooth integration in the coming months. regards, tom. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853455#3853455 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853455 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
