[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipselink-dev] 2.1 Design doc for JMS-MDB cache coordination
|
Hi Chris,
I suppose eclipselink creates a session for the Persistence-Unit-Name that is mentioned in the persistence.xml(if not, then I would suggest that it should); hence it should be sufficient to mention the persistence-unit-name in the MDB to get the instance of RemoteCommandManager.
Hence, the following actions may not be required:
Example MDB’s getSession requires the session name be defined in the ejb-jar.xml under a “tl_session_name_for_mdb” property.
- JPA users will need to either
- define a unique session name in persistence.xml using <property name="eclipselink.session-name" value="MySession"/>
- deploy their own MDB and use EM injection or Persistence.getEntityManagerFactory and the JPAHelper to get the session
How about facilitating the cache co-ordination configuration through persistence.xml, perhaps via extended properties, for JPA users? I could not find that info in the document listed in the mail thread
I would recommend keeping the reference implementation of MDB as a seperate download so as to avoid the dependency on EJB MDB classes.
Please remember that Eclipselink is also used in Java SE environments where EJB is not an available option.
I hope my concerns will be understood and a more JPA friendly solution will be evolved,
Thanks and Regards,
Samba