Envers hbm xml based configuration
----------------------------------
Key: HHH-3887
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3887
Project: Hibernate Core
Issue Type: Improvement
Components: envers
Affects Versions: 3.5
Environment: Hibernate: All Hibernate Versions including Envers as subproject
Our Project: Hibernate 3.3.1, Spring 2.5.6, Spring DM 1.2.0, Swing, GWT, ....
Reporter: Helmut Pasch
Currently the tool library Envers can only be configured / mapped to java POJOs by
annotations. We would appreciate if this mapping could be done by hbm xml files. Using
this approach the POJO won't be bound to Envers annotations. They simply would be
left as POJOs instead of transformed to JPA like Entity Beans.
We use POJOs to directly serialize them to a client tier, e.g. a Swing or GWT client
tier. If our POJOs have to rely on Envers annotations similar like JPA annotations we see
only two options objects may leave the server tier. First by a copy to an annotation less
value object, which is consuming performance and resources. Second by coping / using
Envers / Hibernate libraries for reference purposes on the client tier.
Both solutions are not very attractive compared to the very well working hbm xml approach
Hibernate core ORM functionality provides us. It is our intention to reduce / eliminate in
client server communication model transformations like coping objects or transforming them
to other formats like XML, e.g. like web services does. The easiest way would be to just
serialize the Java POJO objects. But never then less the client should only depend
(logically) on the server API. It is not intended to rely on a specific server
implementation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira