Hi Chuck

Thanks for spotting that one. Steen also spotted it a day or so ago, the fix
is also available in CVS and the daily build.

James
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 14, 2001 9:42 PM
Subject: [dom4j-dev] dom4j-1.1 SAXContentHandler bug


> James,
>
> Line 296 of the released dom4j-1.1 code has a small mistake. It calls
> setInternalDeclarations
> instead of setExternalDeclarations. This doesn't show when using Crimson,
> but when using
> Xerces both internalDeclarations and externalDeclarations are set to NULL.
>
>     public void endDTD() throws SAXException {
>         insideDTDSection = false;
>         if ( document != null ) {
>             DocumentType docType = document.getDocType();
>             if ( docType != null ) {
>                 if ( internalDTDDeclarations != null ) {
>                     docType.setInternalDeclarations(
> internalDTDDeclarations );
>                 }
>                 if ( externalDTDDeclarations != null ) {
>
> BEFORE                    docType.setInternalDeclarations(
> externalDTDDeclarations );
>
> AFTER                     docType.setExternalDeclarations(
> externalDTDDeclarations );
>
>                 }
>             }
>         }
>         internalDTDDeclarations = null;
>         externalDTDDeclarations = null;
>     }
>
> Chuck Simpson
> [EMAIL PROTECTED]
>
>
> _______________________________________________
> dom4j-dev mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dom4j-dev
>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-dev

Reply via email to