Is there any particular reason why OpenJPA uses the 
geronimo-jpa_3.0_spec-1.0.jar instead of the 
http://mvnrepository.com/artifact/javax.persistence/persistence-api/1.0 from 
https://glassfish.dev.java.net/javaee5/persistence/ 
(https://glassfish.dev.java.net/source/browse/glassfish/persistence-api/).  Is 
it OSS Licensing mess, use of a CDDL API JAR in a APL libraray a problem?

BTW: I noticed that the persistence-api-1.0-sources.jar (e.g. from 
http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/persistence/persistence-api/1.0/)
 have JavaDoc... while the geronimo-jpa_3.0_spec-1.0-sources.jar or 
geronimo-jpa_3.0_spec-1.0-javadoc.jar don't.  If you use "Source Attachment" in 
e.g. Eclipse this is handy...

Would there be any risk if locally we overwrote dependencies so that developers 
in our org would use OpenJPA with the persistence-api-1.0.jar instead of the 
geronimo-jpa_3.0_spec-1.0.jar (in order to have JavaDoc Help in Eclipse?).  
Probably not - why would there be?  Is this "allowed" (more out of curiosity), 
license wise?  Presumably yes?

Regards,
Michael Vorburger


-----Original Message-----
From: Patrick Linskey [mailto:[EMAIL PROTECTED] 
Sent: vendredi, 29. février 2008 01:42
To: [email protected]
Subject: Re: multiple persistence-units, each w different provider

Hi,

I think that the official copy is the one at Glassfish.

-Patrick

On Thu, Feb 28, 2008 at 2:15 AM, Adam Hardy <[EMAIL PROTECTED]> wrote:
> I have three persistence-unit nodes in my persistence.xml: one for 
> Toplink with  the toplink provider specified, one for Hibernate, and one for 
> OpenJPA.
>
>  It tests various operations in JPA, configured to use whichever JPA 
> supplier I  specify at the time, i.e. I just change the name of the 
> persistence-unit I pass  to Persistence.createEntityManagerFactory().
>
>  So I have, for instance at the moment, not only openjpa.jar on the 
> classpath,  but also hibernate-entitymanager.jar and toplink-essentials.jar.
>
>  When running my test, due to the way 
> javax.persistence.Persistence.class is  programmed, any of those 
> providers may be picked for use, without reference to  the name of the 
> persistence-unit name that I specified when calling
>  createEntityManagerFactory() - somewhat surprisingly!
>
>  If my memory serves me well, the persistence-api.jar that I am using 
> is just the  one that maven downloaded automatically from the global jar repo.
>
>  I'm tempted to create my own javax.persistence.Persistence to do it 
> properly and  position it ahead of the persistence-api.jar on my classpath.
>
>  This just doesn't seem right. I guess I should be asking at Sun. Was 
> it Sun who  wrote javax.persistence.Persistence ? Or are there 
> different versions? Is there  an 'OpenJPA persistence-api'?
>
>  Has anyone here written their own and made it publicly available?
>
>
>  Thanks
>  Adam
>
>



--
Patrick Linskey
202 669 5907

____________________________________________________________

• This email and any files transmitted with it are CONFIDENTIAL and intended
  solely for the use of the individual or entity to which they are addressed.
• Any unauthorized copying, disclosure, or distribution of the material within
  this email is strictly forbidden.
• Any views or opinions presented within this e-mail are solely those of the
  author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
• An electronic message is not binding on its sender. Any message referring to
  a binding engagement must be confirmed in writing and duly signed.
• If you have received this email in error, please notify the sender immediately
  and delete the original.

Reply via email to