You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Paul Winder <pw...@arbortext.com> on 2001/04/25 19:52:32 UTC
Re: 'd documents do not correctly identify
absolute file paths
Hi Myriam,
It's not really a question of what is a valid URI. The SystemIdResolver
will correctly handle valid URI's. It does not handle some valid system
id's that are not URI's, however, and that is the problem, as I see it.
Paul
At 01:41 PM 4/25/01 -0400, Myriam_Midy@lotus.com wrote:
>Hi Paul,
>I couldn't remember who was involved in this originally. So the question
>about what is a valid URI is still pending. Scott is currently burried
>under DTM stuff, and we'd definitely need his input on this. As soon as he
>gets a chance we can continue the discussion and come up with a solution
>that will make everybody happy (hopefully).
>
>Myriam
>
>
>
>
> Paul
> Winder
> <pwinder@arbor To:
> xalan-dev@xml.apache.org,
> text.com> xalan-dev@xml.apache.org
>
> cc: (bcc: Myriam
> Midy/CAM/Lotus)
> 04/25/01 01:24 Subject: Re: <xsl:import>'d
> documents do
> PM not correctly
> identify absolute file paths
> Please
> respond
> to
> xalan-dev
>
>
>
>
>
>
>
>
>Hi Myriam,
>
>As you know, I filed one of those bugs: [Bug 1323] .
>
>My immediate problem was UNC names, such as
>\\myserver\stylesheets\mystylesheet.xsl.
>The initial stylesheet request was not a problem, but any includes or
>imports failed because the path was interpreted as
>relative. The fix (which was easy to implement but difficult to figure
>out) was to make it a valid URI:
>
> file:///\\myserver\stylesheets\mystylesheet.xsl
>
>This has solved my problem for now.
>
>In my discussions with Scott and (indirectly) Shane, we bogged down on the
>question of whether the SystemIdResolver should be accepting things that
>are not valid URI's. My take on that is that if it is really a
>SystemIdResolver, then it should accept and deal correctly with UNC names
>(which are not in themselves valid URI's) because they are valid Sytem Ids.
>
>I would be happy to work on this bug, since I have already worked with the
>code, but I would need some clarification as to how this is to be
>resolved. I would recommend making the SystemIdResolver truly a
>SystemIdResolver, and have it make System Ids (including UNC's) into valid
>URI's and feed those into what is now called a SystemIdResolver, renaming
>that something like DefaultURIResolver.
>
>Paul
>
>In my discussions with
>At 11:06 AM 4/25/01 -0400, Myriam_Midy@lotus.com wrote:
>
> >Actually we have a couple bugs opened in this area already. We are aware
>of
> >this problem. Any volunteers to fix it are most welcome...
> >
> >Myriam
> >
> >
> >
> >
> > David_Marston@
> >
> > lotus.com To: xalan-dev@xml.apache.org
>
> >
> > cc: (bcc: Myriam
> > Midy/CAM/Lotus)
> > 04/25/01 10:56 Subject: Re: <xsl:import>'d
> > documents do
> > AM not correctly identify absolute
>
> > file paths
> > Please
> > respond
> > to
> > xalan-dev
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > >-- Additional Comments From Alex.Blewitt@ioshq.com 2001-04-25 03:02 ----
> > >The SystemIDResolver searches the uri (file name) for evidence of ':',
> > >and if not found, appends file:///<current_dir>/ onto the front.
> > >
> > >I therefore suspect (though haven't tried it) that using
> > >'file:///tmp/ext.xsl'
> > >will work ok, whereas just using '/tmp/ent.xsl' fails.
> > >
> > >If the SystemIDResolver's getAbsoluteURI method was modified not to
> > >only search for 'file:', but also if it started with '/' as the first
> > >character, that it be treated as an absolute file name.
> >
> >Can someone who uses Xalan on a Macintosh comment on this? Filepaths
> >on a Mac use the ':' as a separator, but if the URI version uses '/'
> >consistently, then his idea should work.
> >.................David Marston