Steve Ebersole wrote:
The bigger issue
here imo is the fact that the nature of XML suggests that we are
discussing structured data; structure which is generally described by a
schema or DTD. What you do not like is the "static" nature of the
Schema can allow for partial documents. The EE 5 schema is one, but
I am not "an XML person". However, I believe there is an
would be great and which XML supports, but I am not certain. I am
talking about representing the association as a "link" (potentially) to
another part of the document describing the associated data on the basis
that it may be shared:
<!- here, an 'employer' element would "link" to the <company
id="1"/> reference below -->
Then, if the association data is uninitialized you would still have the
"link", but the entity data would not be included in the document.
I think that would be a great feature/option and would gladly accept
patches for that.
I've actually been thinking of implementing this, but not in the way you
are talking about. Again, the problems resides with how hibernate
currently implements DOM4J mode and I'm pretty sure that just plugging
in a new tupleizer won't work.
What I'm thinking of is a RESTful approach to interacting with hibernate
over the web and using hyperlinks/URIs to reference
If you wanted more data then just do:
Then for updates send partial documents to server for updating
XML Schema could be used to control how partial a document could be.
Another EntityMode I want to write is a Restful JSON one. I actually
think this might be doable solely by writing a tuplelizer for the
dynamic map mode, so I might prototype this first rather than fuck
around with hibernate at all...
JBoss, a division of Red Hat