digester is an easy way to develop SAX-based content handlers. given enough ingenuity (and effort), you can make just about any xml->object mapping you like. it's (usually) used to create object models from xml. you could create custom rules that execute code but that's not really it's focus.
ant is a java based build tool. ant build files are in xml format. the contents of the build file determines which build tasks should be executed.
the xml has a fixed format for extensions via new taskdefs. ant maps xml to objects internally but it's focused on being a build tool rather than on general purpose mapping.
jelly is a tool for turning xml into executable code - and so it's more like ant than digester. it can be extended by creating custom tags (similar to jsp custom tags). it's more flexible than ant since it's intended for general purpose scripting rather than just building.
if you need a description of the internal working of jelly and ant (in other word, how they do the mapping) then i'd suggest that you ask specifically on the relevant lists (since you're more likely to get a good answer than if i take a guess).
- robert
On Thursday, January 23, 2003, at 07:53 PM, Dominique Devienne wrote:
Can anyone compare (or point to some kind of article comparing) Jelly and
Digester, what they have in common, how they do things differently? Pros and
cons, this kind of stuff. If this could be contrasted to Ant's way of
mapping XML to Java code, that would be even better, but not necessary.
Thanks, --DD
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED].
org>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED].
org>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
