DOMStreamer incompatible changes

[Unico Hommes <Un...@hippo.nl>]

Hi,

There have been a lot of changes made to DOMStreamer lately and I'm grieved to see without consideration of backwards compatibity. For instance the method setContentHandler seems to have been removed completely. I use this class quite heavily throughout my code and I'm getting errors when compiling against cocoon CVS HEAD.

I don't see why this change was deemed neccessary, could anyone please explain? In my code I have several places where a single threaded component has a DOMStreamer instance variable that is used for the lifetime of the component. Whenever it's used I connect the current ContentHandler to it by calling m_streamer.setContentHandler( currentContentHandler ). Please reconsider this change, I don't imagine I am the only one using that class.

Regards,
U.

Re: DOMStreamer incompatible changes

[Bruno Dumon <br...@outerthought.org>]

On Tue, 2003-03-18 at 16:25, Unico Hommes wrote:
[...]
> For
> instance the method setContentHandler seems to have been removed
> completely.

re-added in CVS (both 2.0 and 2.1).

Thanks for reporting, and don't hesitate to report any further problems
you may have.

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