Re: Commons-Digester vs. DOM4J

Hi Carlos.

Digester did the job fine.=20

But first it is a bit slow, since it needs to read and parse an XML file wi=
th rules (possible to code that in Java, I know, but anyway...).=20

The second and major thing is that I think that it has way to many dependen=
cies. It uses commons-logging, commons-collections and commons-beanutils,=
 while dom4j has no dependecies at all.=20

The code for the dom4j implementation is just sligthly longer and more comp=
licated.=20

So I'm sticking to dom4j. :-)

- Jonas

-----Original Message-----
From: Carlos Villela <[email protected]>
To: [email protected]
Date: Thu, 24 Apr 2003 08:46:17 -0300=20
Subject: [aspectwerkz-developer] Commons-Digester vs. DOM4J

Hi Jonas!

Just curiosity: I've been reading the planned tasks for AspectWerkz, and=20
there's a task planned for 0.4 named 'replace digester and all the=20
commons-* libs with dom4j'. Why is that? Having trouble with=20
commons-digester, or just going a little more low-level, to get more 
flexibility?

[]'s
-cv




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
aspectwerkz-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/aspectwerkz-developer


- Jonas



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf