cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Sutic <leo.su...@gmail.com>
Subject Re: Sharing cocoon.jar between multiple web aplications
Date Wed, 08 Sep 2004 19:06:40 GMT
On Wed, 8 Sep 2004 14:32:01 -0400, peter royal <proyal@apache.org> wrote:
> On Sep 8, 2004, at 11:17 AM, ġURDINA Michal wrote:
> > The problem arise only when one web application calls other web
> > application to generate its output (via getRequestDispatcher.include()
> > - crosscontext must be enabled). Then both webapps use the same static
> > field instance in the same thread. And if both are calling method on
> > the same class i.e. Cocoon.process(), then called web application can
> > rewrite the value saved by calling web application.
> 
> ah, gotcha.
> 
> why not just put cocoon.jar per-webapp then, and put the rest of the
> deps at the ear level? :)

Because the other deps may include cocoon components (generators etc).
The cocoon jar will suck all the other libs with it.

The problem seems to be that the stack is assumed to be empty at start
of processing, otherwise it doesn't matter. Would it be possible to
instead put some kind of "barrier" on the stack at startProcessing,
and remove it at endProcessing? It would be empty to the thread
handling the request, because it can't see beyond the barrier.

/LS

Mime
View raw message