cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: XML/HTML serializers buffering everything and using threads.
Date Mon, 24 Feb 2003 17:06:46 GMT
Bruno Dumon wrote:

>On Mon, 2003-02-24 at 13:01, Carsten Ziegeler wrote:
>  
>
>>>-----Original Message-----
>>>From: Bruno Dumon [mailto:bruno@outerthought.org]
>>>Sent: Monday, February 24, 2003 12:47 PM
>>>To: cocoon-dev@xml.apache.org
>>>Subject: RE: XML/HTML serializers buffering everything and using
>>>threads.
>>>
>>>
>>>On Mon, 2003-02-24 at 12:24, Carsten Ziegeler wrote:
>>>[...]
>>>      
>>>
>>>>I personally see this as the right solution... :) I tried to fix this
>>>>bug in Xalan several month ago but failed :( (Ok, I only had three hours
>>>>time to understand whats going on inside Xalan).
>>>>So, best thing in my eyes is to build up some pressure on the
>>>>        
>>>>
>>>xalan team,
>>>      
>>>
>>>>so that they will fix this annoying bug.
>>>>        
>>>>
>>>I assume it is this bug you're referring to?
>>>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5779
>>>
>>>I think that one is a bit in the grey zone: the DOM spec puts the
>>>responsibility for creating correct namespace declaration attributes to
>>>the creator of the document.
>>>
>>>      
>>>
>>The DOM has this extra information
>>    
>>
>
>I know, but the point is that the creator of a dom-tree is responsible
>for adding namespace declaration attributes themselves. Though I agree
>that this is something that is impractical and that the serializer
>should be able to add correct namespace declarations.
>
>I've added a comment to bug
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1831
>in that regard.
>  
>

Guys,

I added a fix in AbstractTextSerializer ages ago in this area : it adds 
in front of the IdentityTransform (it was before the current workaround) 
a "NamespaceAsAttributes" XMLPipe that. adds namespace declarations as 
attributes on the fly, without requiring building the full DOM tree.

Note also that this XMLPipe is added only if needed (there are some 
init-time checks) since some other XSLT processors handle this correctly 
(namely Saxon).

Shouldn't it be an answer to this problem ?

Sylvain (on ski vacation ;-)

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }



Mime
View raw message