Hmmmm....good question. I just started using XmlBeans on our current project to create Java objects from our WSDL XSD schema. I do see some potential problems with the generated objects from XmlBeans. Dozer might have problems with the generated XmlBeans objects. We deal mainly with JavaBeans that have standard get/set methods and standard no arg constructors. XmlBeans has a Factory model to construct new objects as well as myObject.addMyNestedObject() to create new objects on existing references.

For custom creation (using the Factory provided by XmlBeans) you would have to write a custom bean factory (http://dozer.sourceforge.net/documentation/custombeanfactories.html) in order to instantiate XmlBeans objects. If there are standard getter/setters (I can't remember...) on the XmlBeans objects we should be able to handle attribute mapping out of the box.

The best thing to do is create a simple bi-directional mapping and try mapping your objects both ways. Please let me know if you have any more questions.

Take care.

Franz

Mika Göckel <[EMAIL PROTECTED]> wrote:
Franz,

sorry to be off topic :-) Are you the developer of Dozer?
We're just about to use it to bridge the impedance between some of our
service oriented object models and an object model of our existing
application.
Are there any experiences using Dozer together with XmlBeans?

Cheers, Mika


Yahoo! Mail
Use Photomail to share photos without annoying attachments.

Reply via email to