Rafael,

It's a standard j2ee classloading problem. When jbpm.jar is outside the war it 
can not access the classes inside the war. Simply because jBPM creates it's own 
process classloader to load versioned classes from the DB. There is a jira 
issue to (also?) use the context classloader, so jBPM can access classes in the 
war.

Solutions:
- as described above, put jbpm.jar in the war
- or pur the classes in the process archive
- wait for the issue to also use the context classloader to be solved


View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966107#3966107

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966107
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to