Except that you can parameter JBoss to use an "optimization" of its own : UnifiedClassloader :
http://www.jboss.org/community/wiki/classloadingconfiguration > > In jboss-3.2.3, the jbossweb-tomcat41.sar is configured to use a unified > class loader as the web application class loader. This is controlled by the > UseJBossWebLoader attribute in the > jbossweb-tomcat41.sar/META-INF/jboss-service.xml descriptor. The use of a > unified class loader means that the classes available in the war inside of > the WEB-INF/classes and WEB-INF/lib are incorporated into the default shared > class loader repository. This may not be what you want as its contrary to > the default servlet 2.3 class loading model and can result in sharing of > classes/resources between web applications. You can disable this by setting > this attribute to false. > That is, if this setting is activated all webapps are sharing the same classloader, which is of course not J2EE standard, and you can't use two different versions of Wicket. 2009/9/14 Igor Vaynberg <[email protected]>: > if the two apps are deployed as two separate apps then they should not > see each other's jars and therefore should not see each other's > wicket.properties files. > > -igor > > On Mon, Sep 14, 2009 at 4:08 AM, A. Zwaan <[email protected]> wrote: >> Sorry about the late reply, the migration was put on hold for a couple of days as some higher priority project needed some extra resources. >> >> The wicket 1.2.6 jar is in an ear file, which is one of the applications. The 1.4.1 jar is included in a war file, which is the other application. Both are deployed with the same JBoss instance.
