Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 83622 invoked by uid 500); 10 Dec 2001 06:06:23 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 83611 invoked from network); 10 Dec 2001 06:06:22 -0000 Date: Mon, 10 Dec 2001 07:04:10 +0100 (CET) From: giacomo X-X-Sender: To: Subject: Re: Protocol context: question In-Reply-To: <3C13E3C2.9000605@a1.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, 9 Dec 2001, Bernhard Huber wrote: > Hi, > > >>Question 1: Is there any reason why it is not resolved really to the > >>servlet context, hence writing > >>context://cocoon/foo/bar to resolve to the current cocoon servlet context? > >> > > > >Maybe I don't get what you mean. But in your suggestion you have to know > >where the cocoon servlet is deployed and thus the //cocoon/ part of your > >path isn't portable than. > > > In a subsitemap I was using: > > > > > ... > > to access a stylesheet resource. > As I read the docu about context:// it was not clear to me that it is > always relative to the current servlet context. > I was thinking that for example if I have a servlet forum, I may access > an image a.jpeg from this servlet by using > URL context://forum/a.jpeg. > But as I see this is not the indention of usage of context:, Is there > already some URL for accessing > resources of another servlet? Is there a functionallity around your idea supported by a servlet spec/container? Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org