Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: domain of leo.sutic@gmail.com
 designates 64.233.170.205 as permitted sender)
Message-ID: <f41e0a050409081206380c5eea@mail.gmail.com>
Date: Wed, 8 Sep 2004 21:06:40 +0200
From: Leo Sutic <leo.sutic@gmail.com>
Reply-To: Leo Sutic <leo.sutic@gmail.com>
To: dev@cocoon.apache.org
Subject: Re: Sharing cocoon.jar between multiple web aplications
In-Reply-To: <5FF0E7A2-01C5-11D9-8632-000A95AC787E@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <4C47FFB0CC6A2E4D92550B89B68FC7830170C84B@s2-ba.asset-internal>
	 <5FF0E7A2-01C5-11D9-8632-000A95AC787E@apache.org>

On Wed, 8 Sep 2004 14:32:01 -0400, peter royal <proyal@apache.org> wrote:
> On Sep 8, 2004, at 11:17 AM, =C4=8EURDINA 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.
>=20
> ah, gotcha.
>=20
> 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