Re: [eclipselink-dev] A patch file for bug 414974 is now available for r

[Scott Marlow <smarlow@xxxxxxxxxx>]

Any feedback on this change?  I think it would make it easier to use 
EclipseLink with WildFly.  WildFly has  modular classloading which in 
theory could work with multiple versions of EclipseLink.  My concern is 
that currently, users have to set a system property that identifies the 
archive factory to be used with EclipseLink.  If multiple archive 
factories need to be specified, the user will have to pick which one to 
use (which would be limiting).  It is also an extra step for users to 
set the system property.  WildFly documentation that explains how to 
specify the archive factory via a system property is here 
https://docs.jboss.org/author/display/WFLY8/JPA+Reference+Guide#JPAReferenceGuide-UsingEclipseLink

As of WildFly 8.0.0.Final, we are also passing the archive factory via 
an integration property (hoping that the 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=414974 patch will be merged).


On 02/04/2014 08:30 AM, Scott Marlow wrote:
> A patch file for bug 414974 is now available for review.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=414974 contains the patch
> as an attachment.
>
> Description: allow eclipselink.archive.factory to be specified as an
> integration property of
> PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo,
> Map)
>
> Please review and provide any feedback.
>
> Thanks,
> Scott
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev