commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Graham <>
Subject Re: XML Im-/Ex-porter into Commons Sandbox
Date Thu, 07 Oct 2004 21:37:09 GMT
This will create bloat problems for clients that use Digester.  For
example:  Struts uses Digester for xml parsing.  In the future Struts may
want to use the new i18n component.  However, if i18n uses XML Im-Exporter
then Struts must drag that along too despite already having a perfectly
fine xml parser in its dependency list.

Struts is just one example.  It will be even worse for inter-commons
project dependencies.

Bad dependency management has plagued commons components and it's just
recently started to get better.  If all commons components use Digester
then we can avoid having to duplicate functionality and bloat

I don't understand what's wrong with Digester that necessitates a new
parsing library.  I've been able to write complex parsing rules in a
matter of minutes.


--- Oliver Zeigermann <> wrote:

> Folks,
> on the request of Daniel Florey I'd like to create at least one new
> sandbox component for a tool that allows easy import / export of XML
> into / from Java. It is used by Jakarta Slide and in the components
> Daniel introduced.
> I know this is a bit delicate as there already is Digester around in
> commons. However, the audience for my tool is different from
> Digester's. XML Im-/Exporter is geared towards high performance use
> for people who are very familiar with XML. It is just a little bit
> more than pure SAX. It also has a different philosohie than Digester.
> Having said that I hope not to cause any inconvenience with this...
> Preparing this now  and cheers,
> Oliver
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message