cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <je...@apache.org>
Subject Re: DOMStreamer DOM 1 support?
Date Tue, 11 Mar 2003 08:15:53 GMT
On Tue, Mar 11, 2003 at 08:14:21AM +0100, Bruno Dumon wrote:
> 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.

Thanks.  I've put a sample subsitemap that DOMifies an XML stream at
http://cvs.apache.org/~jefft/cocoon/dombug.tgz

--Jeff

> >   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                             http://outerthought.org/
> Outerthought - Open Source, Java & XML Competence Support Center
> bruno@outerthought.org                          bruno@apache.org
> 

Mime
View raw message