[jboss-user] new webapp classloader problem. (I will update the wiki. I promise!)

Hi all, Sorry if this is a basic question, but I've gone through the documentation and various configuration options and still have a classloader issue when trying to deploy a new web-application alongside our .ear file . I wanted to check the list to "make very plain" what I need to do. Here's the scenario: * we use jboss 3.2.6 to deploy "ourapp.ear". * We wanted to deploy Sun's java directory editor webapp "de.war" alongside ourapp.ear, i.e. in the "deploy" directory Here's the problem: * "ourapp.ear" refers to struts 1.1. de.war refers to struts 1.2 (one example of class version issues). Jboss gives classloader exceptions. I have tried the following: * added jboss-app.xml to ourapp.ear/META-INF directory * added jboss-web.xml to de.war's WEB-INF/ directory * tried all four combinations of "JbossWebloader" and "Java2ClassloaderCompliance" in jboss-web-tomcat50.sar/META-INF/jboss-service.xml * I've tried packing the de.war as an ear file and adding de.ear/META-INF/jboss-web.xml I still get problems Problem details: * Either log4j classcast exception or struts classcast exception depending on the values of JbossWebLoader and Java2ClassloaderCompliance * Sun directory editor appears to misbehave if I browse to it before jboss has finished deploying all the references. Question: * I wanted to confirm: do I need to add jboss-web.xml to the de.war? * Is log4j a special problem? i.e. because jboss uses it itself? * I got farther by removing the log4j and loggins-common.jar from the sun 'de.war', but this seems a hack. * Does this sound right? what appears to be incorrect? This problem is fairly well documented, but could use that extra bit of clarity. I will update the jboss wiki with your answer to make the problem idiot proof. I welcome your suggestions. thanks bill m