Deploy the same webapp twice on different paths.

[sbyrne]

I want to deploy the same webapp twice (in my case, two .wars, the only difference is a properties file) on two different paths. It seems that it uses one classloader for both and static variables are not seperated for the two wars. Can I force jboss to use seperate classloaders?
Or is the problem something else?

[sbyrne]

I see two things that might do this to put in jboss-web.xml:

<jboss-web>
 <class-loading>
 <loader-repository>
 dot.com:loader=unique-archive-name
 </loader-repository>
 </class-loading>
</jboss-web>

and

UseJBossWebLoader=false

which should I use?

[sbyrne]

The second option is going to cause problems using jboss's managed connection pool for the database.

[sbyrne]

What I watn to do is have WEB-INF/jboss-web.xml with:

<jboss-web>
 <class-loading>
 <loader-repository>
 dot.com:loader=njportal
 </loader-repository>
 </class-loading>
</jboss-web>

This causes problems with common-logging libraries, resulting in the infamous

cannot find setter method setdocbase null

.

I need the commons-logging.jar in my WEB-INF/lib for struts.

[sbyrne]

Fixed in jboss 4.0.2.