Hi again,
So, I tried to deploy the app to GlassFish v3.0.1 and the same error
occurs. Looks like this may be a general issue with Java EE 5 EAR files
on GFv3.x...
I would love to file a issue for this. However, I fear I may not be
allowed to use our app for this. So I will spend some time creating an
example that shows the same behaviour and will file an issue as soon as
I have one. This may take some time I'm afraid...
Thanks, Wouter
On Tue, Nov 02, 2010 at 10:14:01AM +0100, To quality wrote:
> Hi Richard,
>
>
> Thanks for the tip! When I put the jar containing the Exception class in
> the lib directory of GlassFish, deployment still fails. But now it fails
> on a ClassNotFoundException on a class in a different jar. It looks like
> GlassFish has troubles putting the jars in the ear on the classpath.
>
> Is this a known issue?
>
>
> Thanks, Wouter
>
> On Tue, Nov 02, 2010 at 10:57:25AM +0200, Richard Kolb wrote:
> > Hi Wouter
> >
> > On 2 November 2010 10:47, Wouter van Reeven <wouter_at_van.reeven.nl> wrote:
> >
> > This morning I downloaded build 26 of GFv3.1 and deployed our JEE 5 app
> > on it. Despite some initial issues with project jars that were included
> > in the ear, the app now deploys almost ok. I can see our JPA classes
> > being mapped to the correct tables and views and it all looks ok apart
> > from one small issue.
> >
> > We have created a separate jar with some generic database utilities. Our
> > EJB jar uses those utilities. Upon deployment GlassFish complains about
> > not being able to find an Exception class that is included in the
> > utility jar that is included in the EAR. Basically the error logged is
> >
> > Exception while loading the app : EJB Container initialization error
> > java.lang.NoClassDefFoundError: nl/yenlo/yos4j/exception/
> > NoActiveDatabaseConnectionException
> >
> > Would anyone know how to solve this? Or is this a known bug?
> >
> >
> > I think I know what this issue is, and there is a simple way to test.
> > If you copy the JAR for the nl/yenlo/yos4j/ into you lib instead of including
> > it in your EAR, you probably won't have this problem.
> >
> > If this works, it means that nl/yenlo/yos4j/ is not in the classloader at
> > deploy even though it is in your EAR.
> >
> > There was a similar issue with Vaadin
> > https://vaadin.com/forum/-/message_boards/message/93340#_19_message_99010
> > If you find the glassfish issue, please post.
> >
> > regards
> > Richard
> >
> >
> >
>
> --
> Gravity brings me down
> [Unknown Source]
>
> Skype: wvreeven
> Facebook: wvreeven
> Twitter: wvreeven
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
--
Cloudless everyday you fall upon my waking eyes
inviting and inciting me to rise
And through the window in the wall
Come streaming in on sunlight wings
A million bright ambassadors of morning
[Pink Floyd - Echoes]
Skype: wvreeven
Facebook: wvreeven
Twitter: wvreeven