NoSuchObjectException
Walker Rustin
Ranch Hand
Posts: 37
posted 13 years ago
HFEJB page: 252 qestion 5.
If the client calls a bean that has been removed how come the container could throw either of these.
1)RemoteException
2)NoSuchObjectException
- Walk Rustin
If the client calls a bean that has been removed how come the container could throw either of these.
1)RemoteException
2)NoSuchObjectException
- Walk Rustin
SCBCD
Van Nguyen
Greenhorn
Posts: 23
posted 13 years ago
Walk Rustin
Hi Walker,
the client calls a method from it's remote component object which translates to an rmi call to the "bodyguard" on the container's server. So, the scenerio is either the client has called remove() but later on still uses the ref to the remote component object or the container removes the comp object, and the client has no way of knowing this until he calls on it remotely.
NoSuchObjectException inherits from RemoteException. My guess is NoSuchObjectException is much more informative but that which exception you actually get is container implementation specific.
Hope I didn't confuse things even more.
-Van
Hi Walker,
the client calls a method from it's remote component object which translates to an rmi call to the "bodyguard" on the container's server. So, the scenerio is either the client has called remove() but later on still uses the ref to the remote component object or the container removes the comp object, and the client has no way of knowing this until he calls on it remotely.
NoSuchObjectException inherits from RemoteException. My guess is NoSuchObjectException is much more informative but that which exception you actually get is container implementation specific.
Hope I didn't confuse things even more.
-Van
SCJP 1.4<br />SCWCD<br />SCBCD
