Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Problem parsing XML file with Xerces-J

From: "Michael Kay" <mike@--------.--->
To: "'Midsummer Sun'" <midsummer.sun@-----.--->
Date: 4/1/2005 9:37:00 AM
> 
> 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/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent