aspose file tools*
The moose likes EJB Certification (SCBCD/OCPJBCD) and the fly likes LifeCycle Callback interceptor question Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Certification » EJB Certification (SCBCD/OCPJBCD)
Bookmark "LifeCycle Callback interceptor question" Watch "LifeCycle Callback interceptor question" New topic
Author

LifeCycle Callback interceptor question

Deepak Jain
Ranch Hand

Joined: Aug 05, 2006
Posts: 637
In LifeCycle Callback interceptors , I did not write invocationContext.proceed() has the last statment.
Still the interceptors associated with the buisness method was executed and finally buisness method was executed.
How is this possible ? since if invocationContext.proceed() is not the last statement then the rest of the interceptors
and finally the buisness methods do not execute.



Further the "init" set in ContextData of the above lifecycle callback interceptor was not visible in the other interceptors.
System.out.println("init:"+invocationContext.getContextData().get("init")); in other interceptors returned null. How is this possible?

From EJB IN Action
"That is the whole point of calling the InvocationContext.
proceed method in lifecycle interceptor methods as in the resource
logger code. This ensures that the next lifecycle interceptor method in the invocation chain or the bean lifecycle method is triggered."


SCJP, SCWCD, SCBCD
Christophe Verré
Sheriff

Joined: Nov 24, 2005
Posts: 14688
    
  16

One thing you're not telling us is : do you see all the System.outs from this method in your log ?


[My Blog]
All roads lead to JavaRanch
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: LifeCycle Callback interceptor question