Hi,
OK. I thought this was just for xalan-j. I was wondering why he was trying to
use xerces-c :)
But a couple of questions:
- is it a good idea to do use the EntityResolver to resolve URI's?
- does it handle "document('test.xml', '/foo/poo')"?
- if this gets resolved in the xml parser, what is the result? Is the XML put
into the stylesheet before the transform?
best,
-Rob
> -----Original Message-----
> From: David N Bertoni/Cambridge/IBM [mailto:david_n_bertoni@;us.ibm.com]
> Sent: Thursday, October 17, 2002 1:50 PM
> To: [EMAIL PROTECTED]
> Subject: RE: EntityResolver not allowed to do enough
>
>
>
>
>
>
>
> Let's be very careful not to give advice for Xalan-J for people who are
> using Xalan-C.
>
> There was a patch from a user to let the installed EntityResolver have a go
> at any URLs given to the document() function. I applied this patch, but
> I'm not sure if the provider ever verified it.
>
> Brian, can you provide a minimal set of input files (stylesheet, source
> documents, source code) that illustrates the problem? That way, I can take
> a look at it and see what's going on.
>
> Dave
>
>
>
>
>
> "Robert Koberg"
>
> <[EMAIL PROTECTED]> To:
> <[EMAIL PROTECTED]>
>
> cc: (bcc: David N
> Bertoni/Cambridge/IBM)
> 10/17/2002 01:02 Subject: RE:
> EntityResolver not allowed to do enough
> PM
>
> Please respond
>
> to xalan-dev
>
>
>
>
>
>
> Hi,
>
> > -----Original Message-----
> > From: Brian Quinlan [mailto:brian@;sweetapp.com]
> > Sent: Thursday, October 17, 2002 12:46 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: EntityResolver not allowed to do enough
> >
> >
> > > I think you want a URIRsolver. That is what is used to resolve
> > > document(href, [base]) and xsl:include/import.
> >
> > AFAIK, this API is not available in Xerces-C++, only in Xerces-J.
>
> It is an XSL thing. You set it on the TransformerFactory.
>
> >
> > > What is happening sounds correct. Since you did not supply a base arg
> > > to the document() it uses the stylesheet location.
> >
> > If it doesn't recognize the scheme, I don't think that it should
> > complain until AFTER it has tried the EntityResolver. And unknown
> > schemes should not be considered path fragments.
>
> But document() does not use an EntityResolver. The error is because you are
> sending what looks like a protocol (':') for the default resolver to
> handle.
>
> best,
> -Rob
>
> >
> > Cheers,
> > Brian
> >
>
>
>
>
>
