Ted,
I don't believe the spec makes any such guarantee. Here's the relevant paragraph
from 6.2.1:
The lifecycle of the distributed object implementing the remote home
interface (the
EJBHome object) or the local Java object implementing the local home
interface
(the EJBLocalHome object) is Container-specific. A client application
should be
able to obtain a home interface, and then use it multiple times, during the
client
application�s lifetime.
I don't see any guarantee that the home interface will survive a container
restart. Is there something else in the spec that clarifies or overrides the
above statement?
--Victor
Ted Neward wrote:
> The EJB spec guarantees that a remote reference will never go stale, so long
> as the EJB server is running on the same machine as when the home ref was
> once taken. This is the power of an interception-based framework. The same
> is true of entity bean refs.
>
> Ted Neward
> {.NET||Java} Course Author & Instructor
> DevelopMentor (http://www.develop.com)
> http://www.javageeks.com/tneward/index.html
>
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Catalfano Anthony
> > Sent: Tuesday, September 04, 2001 10:23 AM
> > To: [EMAIL PROTECTED]
> > Subject: [EJB-INT] caching homes on client
> >
> >
> > I'm caching homes on the client side. When I bounce the server, the homes
> > are still in the cache. Is there an efficient way of determining
> > when a home
> > ref is stale?
> >
> > Thanks
> >
> > Anthony Catalfano
> > Information Technology Analyst
> > Deere & Company
> > 309-748-5201
> >
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
