betwixt uses digester for xml->object. it uses the same ideas for simplified mappings that it uses for object->xml.
if you're looking for xml->object mapping then it sounds like you might find digester easier. digester is more flexible and more powerful than betwixt but betwixt makes it easy to read and write common kinds of bean based mapping.
i'd say you should be able to create a digester ruleset for your xml very quickly and it can give you exactly what you want (ie a list). you'll probably find it more difficult to make betwixt do these things.
- robert
On Monday, November 25, 2002, at 12:45 AM, Dan Diephouse wrote:
I have an xml file that is like this:
<?xml version="1.0"?>
<users>
<user>
<username>dan</username>
<password>password</password>
<credentials>
<credential name="read"/>
<credential name="write"/>
<credential name="test"/>
</credentials>
</user>
<user>
<username>testuser</username>
<password>password</password>
<credentials>
<credential name="read"/>
</credentials>
</user>
</users>
Two questions:
1. Can I make BeanReader return a List instead of creating a Users object? If so how?
2. My "User" and "Credential" classes are interfaces. Can I specify to betwixt that it should use an object instead? Or, should I use digester?
I've used it before, but betwixt looks like it could possibly be easier.
Retards,
Dan Diephouse
--
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]>
