This content has been marked as final. Show 4 replies
But we hoped to find a more simple solution than changing our whole application for that.
Option#2 (which is really a workaround if fixing the application packaging is not feasible): The jboss-service.xml file under %JBOSS_HOME%/server/< serverName>/deploy/jboss-web.deployer/META-INF contains this:
<!-- A flag indicating if the JBoss Loader should be used. This loader uses a unified class loader as the class loader rather than the tomcat specific class loader. The default is false to ensure that wars have isolated class loading for duplicate jars and jsp files. --> <attribute name="UseJBossWebLoader">false</attribute>
You can change it to true.