Carsten Ziegeler wrote:
> Hi Berin,
>
> I'm not so happy with this change!
> If you think of Cocoon with having different sitemaps which are located
> in different directories, you have actually different base directories
> for resolving relative to the sitemap in question.
This is where the concept of a Container comes in. More below.
> Or going one thing further, if you thing of a servlet engine having
> several context directories, one for each web application, then you need
> perhaps a SourceResolver for each application.
>
> What do you think?
I understand your concerns, and I have addressed it in this way:
Each Servlet Context is a separate and distinct "container". In Cocoon,
Each Sitemap is it's own container. Therefore, if each Container has
its own Resolver, they all resolve properly.
You just have to make sure that the "container.root" context entry is
set uniquely for each Container.
If you want to make it one Resolver for an entire environment, you either
pass the context with the request, or use the manual base URI entries.
We need to start thinking of the Sitemap as a Container as well as the root
Cocoon object.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
