m: Mark Weaver [mailto:[EMAIL PROTECTED]
> Sent: 03 April 2003 19:21
> To: [EMAIL PROTECTED]
> Subject: RE: EntityResolver doesn't receive the baseURI (repost)
>
>
> My reading of it was that you need an overload for setEntityResolver that
> takes an EntityResolver2 and does the
A while back, I posted a note [1] on how the introduction of
DOMInputSource and DOMEntityResolver will affect the
Xerces-C++ internal components. There was not much of a
response. I hope that this note will give people a good overview
of the how Xerces-C++ works internally. We currently have
two in
> -Original Message-
> From: Gareth Reakes [mailto:[EMAIL PROTECTED]
> Sent: 03 April 2003 16:01
> To: [EMAIL PROTECTED]
> Subject: RE: EntityResolver doesn't receive the baseURI (repost)
>
>
> Hi,
> sorry about the lack of response the first time. Is there
> "Gareth" == Gareth Reakes <[EMAIL PROTECTED]> writes:
Gareth> Apologies, I did not mean this to sound as if I was
Gareth> expecting you to provide anything. I really do mean that I
Oh, I didn't interpret it like that. I was actually intending to write
the code some time in the futur
Apologies, I did not mean this to sound as if I was expecting you to
provide anything. I really do mean that I can do this in short order if
this is helpful to you and is all that is required to be helpful. By new
spec I was referring to the one released at the end of Feb.
Gareth
On 3 Apr 20
> "Gareth" == Gareth Reakes <[EMAIL PROTECTED]> writes:
Gareth> I can change the interface over to the new spec in fairly
Gareth> short order if that would be helpful (or you could provide
Gareth> a patch). Is this all that would be required?
Yes. (new spec? That was the spec way
I can change the interface over to the new spec in fairly short order if
that would be helpful (or you could provide a patch). Is this all that
would be required?
Gareth
> I've been meaning to mention this for a long time now. The official (?
> is 3.0 Load/Save live now) DOMEntityResolver re
> "Gareth" == Gareth Reakes <[EMAIL PROTECTED]> writes:
Gareth> Hi, sorry about the lack of response the first time. Is
Gareth> there a reason why you can't go over to use the official
Gareth> DOM stuff? If so perhaps we should have 2 constructors so
Gareth> we don't break back
Right, got it this time, thanks :)
> -Original Message-
> From: Alberto Massari [mailto:[EMAIL PROTECTED]
> Sent: 03 April 2003 15:59
> To: [EMAIL PROTECTED]
> Cc: Mark Weaver
> Subject: RE: EntityResolver doesn't receive the baseURI (repost)
>
>
> At 1
At 15.35 03/04/2003 +0100, you wrote:
Didn't get any response on this the first time,
Strange, I did answer your e-mail
In any case, what I was telling you is that the EntityResolver interface is
a standard SAX interface, and I guess nobody would like to have it changed.
The proper way to add
Hi,
sorry about the lack of response the first time. Is there a reason
why you can't go over to use the official DOM stuff? If so perhaps we
should have 2 constructors so we don't break backwards compatibility. How
does this sound to you?
Gareth
--
Gareth Reakes, Head of Product Devel
parameter to
the default entity resolver. Objections/comments?
Thanks,
Mark
> -Original Message-
> From: Mark Weaver [mailto:[EMAIL PROTECTED]
> Sent: 22 March 2003 15:15
> To: Xerces-C-Dev
> Subject: EntityResolver doesn't receive the baseURI
>
>
> From an E
At 15.14 22/03/2003 +, Mark Weaver wrote:
From an EntityResolver, I can't see anyway of getting the base URI of the
URI that is passed in for resolution. In some instances I can store it
(e.g. I can do this for the document), but if the document references a
DTD which has imports, then I ca
>From an EntityResolver, I can't see anyway of getting the base URI of the URI that is
>passed in for resolution. In some instances I can store it (e.g. I can do this for
>the document), but if the document references a DTD which has imports, then I can't
>sensibly resolve these. Is this simpl
14 matches
Mail list logo
