Niclas Hedhman wrote:
On Fri, Aug 28, 2009 at 3:02 AM, Alex
Shneyderman<[email protected]> wrote:
Up until recently I did not believe Hibernate was even a possibility,
as I thought it needed java beans to map them to DB, which are not
available in QRM. This however is not a requirement as hibernate has
dynamic-class (this is the old name) feature, where you can stuff a
map with values of named properties and given a hibernate mapping
along, Hibernate is able to persist that map. Sounds like an
EntityState. Very nifty for our requirement to configure everything
on-the-fly.
Ok, if this is the case it sounds reasonable.
Is this part of JPA or is it a Hibernate specific thing? It would be
'even better' if the ES is against the JPA API only (but not a
show-stopper by ay means).
I had a quick look at the JPA JavaDocs, and they all seem to be
POJO-oriented.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
