I'm don't really have an answer for the JPA question, but I am still
interested in knowing if it is possible to recreate the original
exception, since that shouldn't happen no matter what...so I'd like to
investigate it.
-> richard
On 5/20/11 6:58, forums_at_java.net wrote:
> Hello,
> the error is apparently a Glassfish integration issue: the webapp
> deploys
> fine,
> while the 3rd party OSGi application it relies on is not deployed.
> The latter exports eclipselink and java persistence classes on its own.
> After having tried multiple alternatives I removed the persistence
> libs from a 3rd party bundle and the original error disappeared. But now
> other 3party bundles complain about unresolved persistence dependencies.
>
> That boils down to the question, which persistence classes does Glassfish
> export by default ?
> Apparently "org.eclipse.persistence.jpa" is available, but not
> "org.eclipse.persistence.jpa.osgi",
> that is co-packaged and explictely used within the 3rd party bundle:
> PersistenceProvider p = new
> org.eclipse.persistence.jpa.osgi.PersistenceProvider();
> When the Glasfissh' default persistence provider could be used
> instead, this
> would eliminate the need
> for proprietary persistence libs and solve the problem ?
>
> Cheers
> Jaro
>
>
>
>
>
>
>
>
> --
>
> [Message sent by forum member 'jpullmann']
>
> View Post: http://forums.java.net/node/798063
>
>