This is because we use the classloader that loads the jbpm classes as a parent:
public static ClassLoader getClassLoader() {
return ClassLoaderUtil.class.getClassLoader();
}
In case of the default .sar packaging on JBoss, the .sar classloader will not
see your .war classes.
One thing on our todo is make the parent classloader configurable.
http://jira.jboss.com/jira/browse/JBPM-653
If you would be able to specify the context classloader
(Thread.currentThread().getContextClassLoader()), then your problem would be
solved, i guess.
A workaround option is not to use the .sar packaging to deploy jBPM, but rather
to include the jbpm libs (the ones in the .sar) into your .war file.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3943146#3943146
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3943146
-------------------------------------------------------
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
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
