Would not know where writing to XML should go to. Maybe a component of its own?
Concerning merging concepts, there currently are two things I would not know how to integrate into Digester: - sparing a custom stack in many cases where the path object passed with all call backs serves a generic one - having all information about simple elements in a single call back I know Simon is busy now, but maybe we can keep this in mind... Oliver P.S.: Simon, good luck to escape your job hell! On Wed, 13 Oct 2004 12:37:34 +1300, Simon Kitching <[EMAIL PROTECTED]> wrote: > > > On Tue, 2004-10-12 at 22:26, Oliver Zeigermann wrote: > > Folks, > > > > after fruitful discussion with Simon, I think the core of Digster 2 > > might be able to offer everything xmlio offers. My idea would be to > > keep xmlio in the sandbox for now and see if what Simon has for > > Digester 2 really serves everything we need as soon as it is out. If > > so we can drop xmlio. Of course I can offer help with the Digester 2 > > core if this is applicable / wanted. > > > > Daniel, Simon, others, what do you think? > > This sounds good to me. I will definitely have a go at merging the ideas > of xmlio into Digester; currently I think we can, without compromising > the design. > > Note however that this only applies to the "xml reading" part of xmlio. > I don't know what the best thing to do with the "xml writing" part of > xmlio. > > Cheers, > > Simon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
