Carsten Ziegeler wrote: > 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.
Are the changes backward compatible or will they break existing code (apart from readjusting imports)? Can you summarize them here so that everyone of us might check its code and see if and how it works? > 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). This might work only if the API didn't change (I undersand this might be the case for the parser stuff, but what about the others?), otherwise the result might be even worse. I'd go for a) (+1) but I would try to change at least the core classes so that they use the new Avalon implementation. Ciao, -- Gianugo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
