On Fri, 6 Jun 2003 00:01, [EMAIL PROTECTED] wrote: > Brian, > > The XDoclet utilobject pattern caches Remote and (Local Homes the latter > is of course only valid w/in one JVM), I've seen this mentioned on > theserverside.com and elsewhere as a best practice, and after digging > through the spec to be sure, apparently both Remote Homes and Remote > interfaces should be durable even across a server restart (this is what > the spec says -- the references themselves are still valid after a > restart). The only time the references aren't valid is if the beans they > reference have been removed. This is obviously only a problem w/ Remote > Interfaces (not Homes).
I don't think the references them selves are durable, you need to get a javax.ejb.Handle and use that. from it's doco: * The Handle interface is implemented by all EJB object handles. A handle * is an abstraction of a network reference to an EJB object. A handle is * intended to be used as a "robust" persistent reference to an EJB object. and you get these via javax.ejb.EJBObject.getHandle() on the base interface for all the beans. Handle supports on method, getEJBObject() to get back to your reference when you need it. brian... ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
