OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



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

[ Lists Home | Date Index | Thread Index ]

> 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

> 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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS