cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: XInclude processor submitted
Date Thu, 11 May 2000 12:58:48 GMT
Donald Ball wrote:

> > take a look at XSLTProcessor to see how URI relative locations are
> > handled, also you can use the following function
> >
> >  String Util.getRootpath(request, context);
> >
> > to get access to the root path in a servlet API compatible way across
> > containers. (modulo bugs)
> 
> Er, getRootpath is just a wrapper for getRealPath("/"). I think want to be
> using getBasepath (that's what I am doing, anyway). It works as expected,
> at least on JServ. The only real discussion I can foresee here is if
> included relative URLs are relative to the request URLspace or the local
> filespace. I favor the latter, but one could argue a case for the former.
> Probably the XInclude draft should include some mention of this.

The whole mapping point is useless until we finally find a stable
Servlet platform.

I wish we just had one servlet platform :/
 
> > > 3. I haven't read the xpointer or xlink specs very carefully and the
> > > xinclude spec is internally inconsistent. _my_ implementation of an
> > > xpointer parser operates on urls like this:
> > >
> > > href="foo.xml#xptr(/root/child)"
> > >
> > > corrections are welcome.
> >
> > The above is valid, given the latest W3C WD, but may create problems.
> > Here's the explaination:
> >
> > So, my suggestion would be to change "xptr" to "xpointer" even if more
> > verbose and try to be as compliant as possible (Scott, does Xalan
> > support the XPointer extended XPath specification?)
> 
> done.

great
 
> > > 4. circular inclusion checking is not supported.
> >
> > I would not care about this at this time, but in the future we should,
> > add it as a "FIXME" comment in the file.
> 
> actually, nested inclusions won't work at all right now in the cocoon1
> version, now that i think about it, unless the included document is coming
> from cocoon and xinclude processing is turned on. might should figure out
> a way around that, but then again, hopefully xerces will be doing this
> internally before too long.

Ok
 
> > > 5. caching is effectively disabled (this should be relatively easy to fix
> > > though).
> 
> that's already fixed.
> 
> > > all that aside, i think this is a pretty handy module. give it a spin if
> > > you have the time so we can see how portable it is.
> >
> > Sounds awesome.
> 
> standing on the shoulders of giants, that's me.

Don't fool me, man, you wrote more code than I did for this project :)

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------



Mime
View raw message