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 i
Hi, you have to user a classloader per Webapp, so the InjectorHolder has
for each webapp the correct Springcontext. (injectorholder uses a static
variable)
martin
Steve Hiller schrieb:
> Hi All,
>
> I'm not sure if this is a Wicket, Spring or WebSphere issue or some
> combination of the 3.
>
> G
Hi All,
I'm not sure if this is a Wicket, Spring or WebSphere issue or some combination
of the 3.
General Setup:
WebSphere 6.1, wicket 1.3.7, Spring 2.5.6
Specific Setup:
1 EAR contains 2 WARs, call them WAR1 and WAR2.
Each WAR uses the Wicket & Spring frameworks.
The EAR is deployed to WebSphe
