This is true, Joda also performs Java->XML mappings. And like Betwixt it is not intended for use starting from just any old XML. (Java is king, XML is just a data format).
Joda got written because I could find no alternative that met my requirements. JAXB is XML focussed, I needed a Java focussed solution. Castor had an unsuitable licence (you can't use it in a development kit), plus it doesn't support Maps and I found a problem with Lists too. JOX (@sourceforge) was focussed on mapping XML style names to Java ones using a DTD, and also didn't support Maps or infinite recursion. At the time of writing it, I didn't know about Betwixt. Now I am considering if Betwixt and Joda may integrate - not quite sure yet. Joda currently handles Maps and ids in a way I don't think betwixt does yet. But betwixt offers a greater range of output formats and operates on plain JavaBeans.. And as Juozas said, more choice is generally good. Stephen > Hi, > It is also JavaBean-XML mapping framefork : > http://joda.sourceforge.net/ > And it is no problem if you will decide to implement a new one, if you think > it can > be better or have something unique. Users will decide "bad" or "good". > > > > Is there a rundown available on the reasons why Betwix is developing in > > paralel with JAXB? > > > > I've used Castor for quite some time and have been happy with its > > performance. > > Apache Axis build their own JavaBean-XML mapping and Betwix is yet another > > development in the area. > > > > Thanks, > > > > Ivelin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
