[jdom-interest] EntityResolver in JDOMSource

[Laurent Bihanic]

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.

Opinions?

Laurent

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@yourhost.com
> 

-- 
                  wWw    Zzzzz
                 (- -)
-------------ooO-(_)-Ooo-----------------------------------------------
Laurent Bihanic           | Tel: +33 (0)1 55.91.21.93  (Direct line)
Atos Origin               |      +33 (0)1 55.91.20.00
Intégration - e-Business  | Fax: +33 (0)1 55.91.22.31
Les Miroirs - Bat. C      |
18, avenue d'Alsace       |
F-92926 La Defense Cedex  | e-Mail: laurent.bihanic at atosorigin.com
-----------------------------------------------------------------------

"Microsoft isn't the answer. Microsoft is the question and the answer
  is no."


DISCLAIMER:
The opinions expressed are entirely my own and may not necessarily be
those of my employer.  Also, I am not now nor have I ever been a
lawyer.  My opinions are provided as-is with absolutely no warrantee of
merchantability or fitness for any particular use.  Besides, you can't
prove I typed this.  No body saw me type this.  Who says I typed this?