cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <>
Subject Re: Why we have our own SAXParser interface?
Date Mon, 30 Apr 2007 21:45:57 GMT
Carsten Ziegeler napisaƂ(a):
> The main reason was to have a simple bean based implementation that is 
> not tied to Avalon/Excalibur.
> The sax parser is one of our core components so having this inside 
> Cocoon makes sense and reduces dependencies while at the same time 
> allows refactoring the stuff to better fit our needs.

Just to be sure: we should opt for using new interface everywhere in 
Cocoon, right?

Grzegorz Kossakowski

View raw message