> Hi,
> About the discussion about context-relative path:
> Is it allowed to acces from one servlet-context a jsp-file
> residing in some other servlet-context?
> Is this against some security restriction, or servlet-api specs?
> Perhaps some thoughts...
Yes, it's against restrictions, but I think it's not possible, 'cause JSP
engines will treat the given path relatively to the application context.
That was the reason that I started the discussion. Cocoon source resolver
allows external paths, so if you specify a path like '/jsp/file.jsp' then it
will be resolved to a path outside of the app context (for Windows it will
be something like 'file:/jsp/file.jsp').
The 'file:/' prefix can be removed and JSP engine will get a relative to
context path.
When you use 'context://' protocol then path resolves to absolute path and
in this case you'll need to remove the absolute path to context to get a
relative path.
I think that it's a little hacky way. Just thoughts...
Konstantin
>
> ----- Originalnachricht -----
> Von: "Piroumian, Konstantin" <[EMAIL PROTECTED]>
> Datum: Montag, September 3, 2001 9:55 am
> Betreff: Re: [C2] Source path relative to servlet context
>
> > > On Thu, 30 Aug 2001, Piroumian, Konstantin wrote:
> > >
> > > Konstantin, I really don't know why you need that. It has worked for
> > > months now and why should we change URLFactoryImpl and what do
> > we gain?
> >
> > I didn't ask you to change anything, I only needed an advice about
> > that. I
> > need a relative to context path, because I have to pass that path
> > to a JSP
> > servlet (any, not only Apache Jasper), otherwise it won't work.
> >
> > > I think either JspServlet is wrong or your implementation of the
> > > jsp-reader, don't you think? I would like you to try to use the
> > > HttpContext in your jsp-reader to determine the context relative
> > portion> of the src value.
> >
> > I am using that method now (thanks to Vadim Gritsenko who gave me the
> > hint). The JspServlet is not wrong - it works as expected by the
> > specification (Servlet ans JSP). The implementation of JSPReader
> > is in work,
> > so it is possible to be wrong ;)
> >
> > Btw, I tried to make my JSPReader Contextualiazable, but it seems that
> > contextualize method was never called. What's can wrong: a reader
> > cannot be
> > contextualizable or I do something wrong?
> >
> > Thanks for any help.
> >
> > >
> > > Giacomo
> > >
> > > > Hi, all!
> > > >
> > > > Can anybody help me with path resolution? I need a path
> > relative to the
> > > > servlet context, which I will pass to JspEngine/JspServlet for
> > processing.
> > > > In my sitemap I have:
> > > >
> > > > <map:match pattern="test/welcome.htm">
> > > > <map:read src="path-to-jsp/welcome.jsp" type="jsp"
> > > > mime-type="text/html"/>
> > > > </map:match>
> > > >
> > > > When I use an absolute path path-to-jsp = "/jsp/welcome.jsp"
> > then this
> > > > resolves to "file:/jsp/welcome.jsp" and I strip the "file:"
> > and pass
> > > > "/jsp/welcome.jsp" to JSPEngine and this works.
> > > >
> > > > When I use path-to-jsp = "context://jsp/welcome.jsp" the path
> > resolvesto an
> > > > absolute path, say:
> > "file:/C:/tomcat/webapps/cocoon2/jsp/welcome.jsp"and
> > > > JspServlet calls getRealPath() with this and gets the path
> > prefixed with
> > > > servlet context path twice. And of course it gives File Not
> > Found error.
> > > >
> > > > The same thing happens with relative path path-to-jsp-dir =
> > > > "jsp/welcome.jsp". I get an exception because of a wrong file
> > path and
> > File
> > > > Not Found error is returned.
> > > >
> > > > So, to conclude all this: I need a path relative to the
> > servlet contex.
> > > > /jsp/welcome.jsp ==> /jsp/welcome.jsp
> > > > jsp/welcome.jsp ==> <request-path>/jsp/welcome.jsp
> > > > context://jsp/welcome.jsp ==> /jsp/welcome.jsp
> > > > etc.
> > > >
> > > > Are there any hints where do I start? Somewhere in URLFactoryImpl?
> > > >
> > > > Any help is very appreciated.
> > > >
> > > > Regards,
> > > > Konstantin Piroumian
> >
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
>
>
----------------------------------------------------------------------------
----
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
