Shared classloaders in JBoss 3.2.3?

[mbourgeois]

Has anyone seen that 3.2.3 seems to be sharing classloaders across deployed applications? Is this a known bug?

Here's what I'm seeing:
I've got two applications deployed with the same MVC libraries on 3.2.3, and I'm finding that the second application loaded (seems to load apps alphabetically) is set to the first's loaded static variables.

I.e.
A_Application has some static variables that set path's to local resources upon loading.
B_Application seems to be using A's values.

[juha]

This is the default configuration behavior. Add a <loader-repository> tag to your deployment to isolate the classloaders.

[mbourgeois]

I can't seem to find the right place for this. Can you confirm what you mean by add a <loader-repository> tag to my deployment? I've found some references to this online, but nothing that will work for me. Thanks in advance!
Mike

[juha]

Depending on your package type, jboss.xml, jboss-app.xml, etc. The DTDs are included with your JBoss distro.