cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <>
Subject Re: DOMStreamer DOM 1 support?
Date Tue, 11 Mar 2003 07:14:21 GMT
On Tue, 2003-03-11 at 07:37, Jeff Turner wrote:
> Probably a question for Bruno..
> The NamespaceNormalizingDOMStreamer doesn't support DOM 1 nodes, which
> means that any code using, say, 'setAttribute' instead of
> 'setAttributeNS' causes cryptic errors like:

Ah, didn't know that. I thought that it would automatically assign a
value to localName also when using setAttribute (or createElement for
that matter).

Since this is not the case, I'll need to improve the DOMStreamer. I'll
look into it and let you know more later on.

>   Failed to execute pipeline.: org.xml.sax.SAXException:
>   [NamespaceNormalizingDOMStreamer] Encountered an attribute without a
>   local name, this DOM streamer does not support that.
> I haven't looked closely, but is there some reason why
> NamespaceNormalizingDOMStreamer couldn't stream DOM 1 nodes as well as
> DOM 2?  Otherwise, this is going to be a major break of binary
> compatibility with 2.0.

Bruno Dumon                   
Outerthought - Open Source, Java & XML Competence Support Center                

View raw message