• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NoSuchObjectException

 
Walker Rustin
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Van Nguyen
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Vishwa Kumba
Ranch Hand
Posts: 1066
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also both happen to be rmi exceptions, a part of the JDK and not the javax.ejb package.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic