Thanks Martin! That did the trick. Here's some info for other developers "fortunate" enough to work with IBM's WebSphere:
Firstly, IBM's docs claim that, by default, each application server instance has a WAR class loader policy in which a different class loader is used for each WAR file. This is not true: I checked my local server (installed with Rational Software Architect), dev, QA and prod servers. All of them were set to using a single class loader for all WARs within an enterprise application. I was not asked how to set this policy when I installed RSA on my machine. Secondly, there seems to be a bug that prevents changing the WAR class loader policy when working within RSA. That is, that policy setting was in read only mode when displayed in the WebSphere admin console (aka the Integrated Solutions Console). The solution seems to be as follows: 1) In RSA, double click on the WebSphere 6.1 server displayed in the Servers view; this opens the Server Overview window. 2) In the Server Overview window, go to the Publishing section and uncheck the "Minimize application files copied to the server" setting. 3) Save the change. 4) Restart the server. 5) Start the admin console. 6) Select an enterprise application, 7) Click "Class loading and update detection" 8) Set the "WAR class loader policy" to "Class loader for each WAR file in application" 9) Apply and save the change. -- View this message in context: http://www.nabble.com/1-EAR%2C-2-WARs-causes-Spring-Context-Problem-tp25684384p25696859.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
