#30 Support XMLBeans objects

[Anonymous]

Currently, BeanKeeper cannot be used with objects generated from XML by XMLBeans.

Robert said: "it would be great, if you could help us to find out. First, you should describe what you're trying to do, and then locate those points in which BeanKeeper need to be improved to support your setup. I would fix BeanKeeper, if you could identify which things should be fixed."

1. Scenario: data is passed to application via XML.

Instead of parsing XML directly, lazy developer uses XMLBeans to create appropriate Java objects from XML for her. Then, instead of writing SQL queries, the lazy developer uses BeanKeeper to persist these objects. Laziness, laziness.

2. BeanKeeper issues: BeanKeeper currently requires all objects to have a default constructor, and it uses the default constructor to instantiate objects upon find(). Neither would work with objects generated by XMLBeans.

2.a. Save(): to support XMLBeans, upon save() BeanKeeper would need to check whether the object is an instance of org.apache.xmlbeans.XmlObject. If so, it should not require default constructor on save()

2.b Find(): on find(), instead of using the default constructor, use
[name of generated class, extends XmlObject].Factory.newInstance()

If the object is of type MyBean, this would be MyBean.Factory.newInstance().

[Oleg Ryaboy]

Sorry, forgot to log in - this was my request from way back. It is not high priority for me, since I have a workaround.