[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Problem parsing XML file with Xerces-J

• To: "'Midsummer Sun'" <midsummer.sun@g...>
• Subject: RE: Problem parsing XML file with Xerces-J
• From: "Michael Kay" <mike@s...>
• Date: Fri, 1 Apr 2005 10:35:09 +0100
• Cc: <xml-dev@l...>
• In-reply-to: <bb5e8b86050401012539223f33@m...>
• Thread-index: AcU2nMbqvD9wAMpKScaOyQEHmjyNAwAAQwQQ

 
> 
> My 2 questions are unanswered:
> 1) Which method is faster - implementing EntityResolver or pre-editing
> the XML file. This consideration is important for me. My program is
> pooling a remote process very frequently(every 15 seconds) and
> fetching the XML documents. If these 2 methods have some performance
> difference, then response time of my program will be slow in one of
> the case. So I must select whichever is fast.
> 
> I am sure somebody has the answer..

I doubt anyone has the answer. The difference is likely to be unmeasurably
small.

> 
> 2) Is there a way to "not create" a redundant resource (like 
> x.dtd below)
> 
>  public InputSource resolveEntity(java.lang.String publicId,
>                                    java.lang.String systemId)
>  {
> 
>      InputSource is = new InputSource();
>      is.setSystemId("file:///C:/x.dtd");
> 
>      return is;
>  }

I gave you the answer to this right at the beginning: create an InputSource
based on a StringReader that reads the String "".

Michael Kay
http://www.saxonica.com/

• References:
  • Re: Problem parsing XML file with Xerces-J
    • From: Midsummer Sun <midsummer.sun@g...>

• Prev by Date: Re: Problem parsing XML file with Xerces-J
• Next by Date: Re: REST, SOAP, Speech Acts and the mustUnderstand model of SOA communications (was: Re: What Does SOAP/WS Do that A REST System Can't?)
• Previous by thread: Re: Problem parsing XML file with Xerces-J
• Next by thread: Re: Problem parsing XML file with Xerces-J
• Index(es):
  • Date
  • Thread