you definately want to go with a single .ear for your application in
production and final testing. That should make for easier management and
will also enable optimized calls (no copying of method parameters).
OK, so the optimized option only works for beans within the same .ear?
/ Jonas
Since you have a reference to objects that have a reference to the old
versions of the classes, the old versions of the classes can't be
discarded.
Have you tried this with a full .ear deployment? (from below I assume
that you're deploying the servlet and EJBs separately) .ear deployment
:[EMAIL PROTECTED]]On Behalf Of danch (Dan
Christopherson)
Sent: Friday, June 29, 2001 5:48 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Undeployment problem (still)
Since you have a reference to objects that have a reference to the old
versions of the classes, the old versions
Jonas Bergström wrote:
Since you have a reference to objects that have a reference to the old
versions of the classes, the old versions of the classes can't be
discarded.
I don't quite understand. Method invocations through the remote references
goes through the container, right, and I
