RE: [eclipselink-dev] 2.1 Design doc for JMS-MDB cache coordination

[James Sutherland <JAMES.SUTHERLAND@xxxxxxxxxx>]

> that would be a great feature.  Unfortunately, the only way to configure cache coordination in JPA is through code configuration in a customizer.

Note that there has been JPA persistence unit properties to configure cache coordination since the 1.2 release.

http://www.eclipse.org/eclipselink/api/1.2/org/eclipse/persistence/config/PersistenceUnitProperties.html


-----Original Message-----
From: Christopher Delahunt 
Sent: Monday, February 01, 2010 8:57 AM
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] 2.1 Design doc for JMS-MDB cache coordination

Hello Samba,

Thank you for your feedback.  Some comments are inline:

Samba wrote:
> 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
>           o define a unique session name in persistence.xml using
>             <property name="eclipselink.session-name" value="MySession"/>
>           o deploy their own MDB and use EM injection or
>             Persistence.getEntityManagerFactory and the JPAHelper to
>             get the session
>
 > Yes, I guess the second point wasn't clear.  The example MDB used a
session name, which would be used for people using sessions.xml and
users specifying the session name using the eclipselink.session-name in
persistence.xml.  The alternative is to get the EntityManager from the
container or using SE mode, and then use the JPAHelper to get the
session from it.
>
> 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
>
 > that would be a great feature.  Unfortunately, the only way to
configure cache coordination in JPA is through code configuration in a
customizer.
> 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.
 > agreed.  The method of getting the MDB out there still needs to be
worked out.
> 
> I hope my concerns will be understood and a more JPA friendly solution
> will be evolved,
> 
> Thanks and Regards,
> Samba
>
> 
> On Fri, Jan 29, 2010 at 1:48 PM, christopher delahunt
> <christopher.delahunt@xxxxxxxxxx
> <mailto:christopher.delahunt@xxxxxxxxxx>> wrote:
>
>     https://bugs.eclipse.org/bugs/show_bug.cgi?id=214534
>     Patch uploaded for review and feedback
>
>
>     Best Regards,
>     Chris
>
>
>     christopher delahunt wrote:
>
>         Design documentation can be found here:
>
>         http://wiki.eclipse.org/EclipseLink/Development/2.1/JMSCacheCoordinationUsingMDB
>         <http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/undelimited_identifiers>
>
>
>         Please provide feedback either by replying to this email or
>         using the Wiki discussion page.
>
>         Thanks,
>         Chris
>         _______________________________________________
>         eclipselink-dev mailing list
>         eclipselink-dev@xxxxxxxxxxx <mailto:eclipselink-dev@xxxxxxxxxxx>
>         https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
>
>     _______________________________________________
>     eclipselink-dev mailing list
>     eclipselink-dev@xxxxxxxxxxx <mailto:eclipselink-dev@xxxxxxxxxxx>
>     https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
>  
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev