Re: [eclipselink-users] EclipseLink OSGi bundles deployment in Tomcat (w

[Tom Ware <tom.ware@xxxxxxxxxx>]

Hi Azrin and Tim,

  There was an issue with our automatic classloader detection.  It is resolved 
in the EclipseLink 1.0.1 stream as part of a cleanup we did of the code when we 
fixed bugs 238474 and 239841.  The workaround is to supply the classloader (as 
you have done).

-Tom

Tim Hollosy wrote:
> I should have noticed that Azrin,
> I don't think it's a bug, it's just the original comics example is quite old.
>
> ./tch
>
>
> On Tue, Jul 22, 2008 at 1:56 AM, azrin masfian <azrin.masfian@xxxxxxxxx> wrote:
> > Hello Tom and all,
> >
> > I have managed to solve the issue (for both running in Eclipse and outside
> > Eclipse in Tomcat with ServletBridge). The Entity Manager Factory has to be
> > created by passing in classloader of the current class (likewise in one of
> > the comic OSGi bundle example -
> > org.eclipse.persistence.demo.jpa.osgi.spi.classloader). The normal way
> > (org.eclipse.persistence.demo.jpa.osgi.spi) does not work (for both). Can
> > you actually verify that this is actually a bug?
> >
> > Thank you and Regards,
> > Azrin.
> > _______________________________________________
> > eclipselink-users mailing list
> > eclipselink-users@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/eclipselink-users
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users