Mitesh Meswani wrote on 08/28/09 10:28:
Tom Ware wrote:
I am not fond of having a default version of EclipseLink ever allow
itself to be selected when the user has specifically requested
TopLink Essentials in their persistence.xml.
Bill's suggestion of some kind of an add-on is more palatable to me
if we decide we want to have a way of having EclipseLink select
itself in place of Essentials.
I think I am not clear about what that means in terms of
implementation. Can we explore that a bit. Here is my understanding
if we go that route:
* Add (say) org.eclipse.persistence.jpa.ToplinkPersistenceProvider
that extends org.eclipse.persistence.jpa.PersistenceProvider and
related PersistenceInitializationHelper (say)
ToplinkPersistenceInitializationHelper
* ToplinkPersistenceInitializationHelper would wire up a subclass of
JavaSECMPInitializer that would accept Toplink as provider
* Will above classes be part of default eclipselink distribution as
part of eclipselink.jar and org.eclipse.persistence.jpa.jar?
I was thinking that the class would have the exact class name of the
TopLink provider - oracle.toplink.essentials.whatever. No magic would
be needed to translate the class name in the application to the actual
class being used. Ideally, that new class would be the one that would
translate the property names, but I don't know how this all fits together
to know if that's the right place to put that functionality.