cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject Re: DOMStreamer DOM 1 support?
Date Tue, 11 Mar 2003 11:39:18 GMT
On Tue, 2003-03-11 at 09:15, Jeff Turner wrote:
> 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
> 

The DOMStreamer should now also work with elements or attributes created
with createElement or setAttribute (instead of their *NS variants). I'm
still going to do some more testing and performance improvements, but
functionally it should work.

Your dombug testcase also works (though I didn't try it before my
changes so I don't know the difference, but it does not give
exceptions).

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


Mime
View raw message