Johan, The main issue here is that classes need to be found by the classloader on deploy-time, since they are instantiated for caching purposes.
If you use the JBoss integration, you could put these dependencies in the userlibs folder. The other 'workaround' is to have the deployment of processes in your webapp itself. Eg write an EJB to deploy the processes, so that your domain classes can be found on the regular classpath. But thanks for pointing us to this issue. We'll definitely have a discussion on how to ease the development in regular web apps. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243771#4243771 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243771 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
