Brian, You say the problem only appears when you get a JAXR connection factory from within an action handler. Handlers are loaded with the process class loader, whose parent is the loader for the jBPM library (i.e. the service archive loader). The context class loader is skipped (the classes and libraries in your webapp are not searched).
In the end you don't specify where you actually place the libraries. That'd be useful. Right now I'd package them in the jBPM service archive (if you only use JAXR in jBPM processes) or put them in the lib/ subdirectory of the JBoss configuration you are using (if you use JAXR in other applications). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922505#3922505 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922505 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
