cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject RE: Problem with HTMLGenerator
Date Fri, 28 Feb 2003 11:17:19 GMT
On Fri, 2003-02-28 at 09:12, Carsten Ziegeler wrote:
> Bruno Dumon wrote:
> > 
> > On Thu, 2003-02-27 at 22:14, Miles Egan wrote:
> > > After updating cvs and rebuilding I get this error when using the 
> > > HTMLGenerator:
> > > 
> > > [NamespaceNormalizingDOMStreamer] Encountered a DOM Element without a 
> > > localName. DOM Level 1 trees are not supported by this DOMStreamer.
> > > 
> > > Is this a bug?
> > 
> > No, it's a feature :-)
> > 
> > Currently the NamespaceNormalizingDOMStreamer only supports
> > namespace-aware (= dom level 2) DOM trees. Extending it to support DOM
> > level 1 trees would require to put the namespace-processing that
> > normally happens in an XML parser, to be put in the DOM-streamer.
> > 
> > I think the easiest solution for now is to use the default DOM streamer
> > in the HTMLGenerator. I'll fix that in a moment...
> > 

BTW, I did this already last night, but my commit mails don't seem to
get through to the xml-cocoon2-cvs list. Do I need to subscribe with my
@apache.org address to that list?

> Is it possible to test the DOM if it is level 2 or level 1 in the
> DOMStreamer and then if it is level 1 perhaps use the streaming?
> 

A simple test would be just checking that getLocalName() on the root
node doesn't return null, so yes, it is possible.

> In general, most components in Cocoon assume that a DOM is level 2
> which means, namespace aware, so a level 1 DOM should really be avoided.

Yep, that's what I thought.

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


Mime
View raw message