> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > HI, > > as you all know, some time ago we decided to move some of the general > components to Avalon Excalibur. > The first components now finished (hopefully) in avalon are the parser > abstraction and a new source handling. > > The question is now, how to reintegrate these new components? > The interface have - of course - changed. First, there are new package > names and second some methods were changed, added etc. > > So, as expected, this has the problem that the (re)integration is not > so easy. > > As a first running component, I would like to use the "new" parser > abstraction. > > I see 2 possibilities to integrate it: > The first step would always be the same: > Declaring a new role "xml-parser" which is implemented by the avalon > version and change every use in cocoon from "parser" to "xml-parser". > > and then: > a) Leaving the "parser" role as it is for compatibility and deprecating it. > b) Changing the implementation for parser, so that it actually uses the > "xml-parser". This would result in the same interface but of course in > the lookup of two components if a parser is required. > > The advantage of b) is, that each component using the old "parser" role > automatically gets the new "xml-parser" (wrapped by the old one). > > I'm +1 on a). > > Comments?
Shall we roll out intermediate 2.0.1 release before this? We had quite a lot of changes since 2.0, including abandoning cocoon_20_branch. Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
