The problem of the unclean undeployment is not Eclipse related. You will have the same problem if you do a lot of deploy and undeploy cycles using e. g. the admin GUI or asadmin CLI. It is a bug in GlassFish v2. To workaround it, stop and restart GlassFish between (and / or) after deploy and undeploy. Yes, it is annoying, but it helped in our case. In Eclipse, there can be another problem: If GlassFish is started in the same VM that also runs the IDE, then it might be the case that the IDE did not correctly release some files. We had a similar issue with Eclipse Europa. It just kept a lock on some JARs after creating it and we always had to shutdown the IDE to be able to modify the archive. In Eclipse Ganimede it was gone.
Regards
Markus
> -----Original Message-----
> From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
> Sent: Samstag, 27. Dezember 2008 03:36
> To: users_at_glassfish.dev.java.net
> Subject: Re: RE: Re: RE: ResourceAdapter (JCA) from EJB, in EAR
>
> Thanks again. I did not understand that you meant
> ClassNotFoundException when you meant could not be found. I thought you
> meant cannot be found in JNDI.
>
> I work from Eclipse and I think that Eclipse does not undeploy properly
> when you add and remove projects, because your workaround did not work
> there.
>
> But now I got it working! Thanks for your help!
> [Message sent by forum member 'jeltejansons' (jeltejansons)]
>
> http://forums.java.net/jive/thread.jspa?messageID=323372
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net