Looking for the same thing: some example/help on implementing EntityPersister. In my case I want to persist a mix of data, some data from a relational DB and some not, all within the Hibernte Session/Transaction persistence interface. One interface for the end developer, so they don't know/care where the data is persisted. It looks like implementing EntityPersister is the strategy for that, right?
An alternate approach would be to layer my own session/transaction interface over hibernate and handle non-database data completely outside of Hibernate. However, it is attractive to plug into the Hibernate infrastructure for session, transaction, caching, etc.
This seems like a design concept that Hibernate would want to support, taking the persistence abstraction beyond just relational databases. Can anyone provide some advice on this issue?
Thanks,
Greg
|