[jdom-interest] EntityResolver in JDOMSource
pallo at dig.de
Mon Aug 19 22:52:20 PDT 2002
thanks for response, i thought about this, question is if anybody knows why
it is created everytime ?
On Monday 19 August 2002 17:57, Laurent Bihanic wrote:
> The method getXMLReader returns a DocumentReader which extends JDOM's
> SAXOutputter and you can register an EntityResolver on a SAXOutputter
> instance. The problem with JDOMSource is that it allocates a new
> SAXOutputter instance everytime getXMLReader is called (concurrent use of
> the same JDOMSource instance???). Hence all your settings get lost.
> The solution to this problem would be to have JDOMSource allocating only
> one DocumentReader so that the application could configure it before the
> JDOMSource be passed to the XSL transformer.
> Markus Pallo wrote:
> > Hello,
> > i am using JDOMSource for XSLT Transformation and have a own SystemID
> > set. The transformer is unable to parse the dtd(he cannot find it). Thats
> > true, because i am not able to set our own EntityResolver in JDOMSource.
> > Is it possible in the inner class DocumentReader of JDOMSource to set a
> > EntityResolver ?
> > Any other Suggestions ?
> > Thanks for your help
> > Markus Pallo
> > DIG GmbH
> > GERMANY
> > www.dig.de
> > _______________________________________________
> > To control your jdom-interest membership:
> > http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@your
More information about the jdom-interest