The Bindmark results show raw performance for just reading and writing
XML to/from Java objects, with minimal accessing of the data from the
objects. The point I was making in my email is that XMLBeans appears to
add a lot of overhead to the actually accessing of data values from the
data
Here is some info reference material to substantiate or reflect on regarding XML / Binding:
https://bindmark.dev.java.net/
Thought it may help going forward.Dennis Sosnoski [EMAIL PROTECTED] wrote:
Actually, I don't think XMLBeans classes work that well as value objects (I assume that's what you
Actually, I don't think XMLBeans classes work that well as value objects
(I assume that's what you mean by VO). I tried converting a web services
test program I'd written to Axis2 using XMLBeans classes for the data,
and was stunned to see the performance drop by a factor of up to 10
compared
to
user@xmlbeans.apache.org
To
user@xmlbeans.apache.org
cc
Subject
RE: Persisting XMLBeans to DB
I know of the difficulty of using hibernate with XmlBeans. I remember that someone researched some option that hibernate had to use factories instead of default constructors, but I
PMTo: user@xmlbeans.apache.orgCc:
user@xmlbeans.apache.orgSubject: RE: Persisting XMLBeans to
DB
Yeah me neither. I'd like to be able to extend those classes to add
different methods (for persistance) but it doesn't look like extending these
things would work. I'd have to contain the xmlbean
5 matches
Mail list logo
