Thanks for the response... I tried to scope the deployment, using the jboss-web.xml file as described at http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration like this:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.3//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd";> <jboss-web> <class-loading java2ClassLoadingCompliance='false'> <loader-repository> ifmwam.war:loader=ifmwam.war <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </class-loading> </jboss-web> But got the same problems. Should something be different in this descriptor? I did get the WAR file to deploy, finally, but only by placing the JAXP-api.jar & the jaxp endorsed jar files in \lib\endorsed under the JDK JBoss is using. This is OK for testing, but I need to find a less complicated solution for distribution... >From what I read, it would seem that the scoping solution should work. You >mentioned a testcase in JBoss 4.0.x -- is there a problem with scoping the >deployment in 3.2.6? Does it just need to be done differently than the >descriptor I put together above? Thanks again, -- Alex View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938012#3938012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938012 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
