On Fri, 7 Dec 2001, Bernhard Huber wrote: > As I was using the context:// protocol. > The documentation says: > > * context:// - get a resource using the servlet context > > Now it would be better to say get a resource using the current servlet > context. > As context://foo/bar is resolved relative to the current servlet context. > > 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. Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
