This week's giveaway is in the EJB and other Java EE Technologies forum.
We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line!
See this thread for details.
The moose likes EJB Certification (SCBCD/OCPJBCD) and the fly likes Exceptions in lifecycle callback methods (II) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Certification » EJB Certification (SCBCD/OCPJBCD)
Bookmark "Exceptions in lifecycle callback methods (II) " Watch "Exceptions in lifecycle callback methods (II) " New topic
Author

Exceptions in lifecycle callback methods (II)

Ralph Jaus
Ranch Hand

Joined: Apr 27, 2008
Posts: 342
The ejb core spec says (12.4.2, page 307):
A runtime exception thrown by any lifecycle interceptor callback method causes the bean instance and its interceptors to be discarded after the interceptor chain unwinds.
Doesn't glassfish fulfill this requirement or is something wrong in the following example ? If I call test() from the client two times the output in the
log looks like

IA
warning: myException
test
test

But at least the second "test" output wouldn't be possible if the bean had been discarded after the interceptor chain unwinds. What do you think ?
[ October 21, 2008: Message edited by: Ralph Jaus ]

SCJP 5 (98%) - SCBCD 5 (98%)
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Exceptions in lifecycle callback methods (II)
 
Similar Threads
Callbacks with System Exceptions
Lifecycle callback interceptor
Multiple life-cycle Callback methods per class
Exceptions in lifecycle callback methods (I)
LifeCycle Callback interceptor question