Giacomo Pati wrote:
Reinhard Poetz wrote:
Giacomo Pati wrote:
Giacomo Pati wrote:
Reinhard Poetz wrote:
Before I'm going to release the Cocoon Maven plugin, I worked on the
XPatcher for the web.xml. All .xweb snippets now get rewritten so that
the ReloadingClassloader interceptors get applied to filters, listeners
and servlets.
As I was at it I also implemented a wrapper around the "normal" Spring
web application context. It takes care of context reloads internally
and
is completly synchronized. Giacomo reported that he had problems when
you accessed the Spring application context from outside of Cocoon,
e.g.
from within a servlet filter. This _might_ be helpful in that case
though I haven't tested it yet.
I'll test it today, thanks.
Now here are my results: It doesn't work as expected!
That's strange :-(
What do I have to do to reproduce it? Is writing another servlet that
accesses the Spring application context enough?
To be honest, I have no clue :-( I've simply configured acegi into the web.xml
(as a patch) and at
the second request mentioned stacktrace is thrown.
I have never used acegi but will give it a try.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
