i have exactly the same problem, and your description of its behavior is very
accurate. I want to find out a way to test whether the bean is still valid.
my stupid way to do it is this. i have a public void dummy() method in the home
interface and the bean. then in the client i have
try {
home.dummy()
} catch(Exception e) {
try {
home = (BeanHome)lookup("beanName");
} catch(Exception e){}
}
i admit it's very stupid but that's the only way i can think of for now.....
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844050#3844050
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844050
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
