This content has been marked as final.
Show 3 replies
-
1. Re: destroying the entire conversation stack through annotat
jacob.orshalick Aug 27, 2007 11:53 AM (in response to jacob.orshalick)By the way, I am currently using Seam 2.0.0.BETA1.
I have come up with a potential patch that would allow the existing @End annotation to perform this task:
In org.jboss.seam.annotations.End add the following:boolean endRoot() default false;
and then in the org.jboss.seam.core.ConversationInterceptor.endConversationIfNecessary():... boolean endRoot = ( isEndAnnotation && method.getAnnotation(End.class).endRoot() ); ... private void endConversation(boolean beforeRedirect, boolean endRoot) { Manager manager = Manager.instance(); if(endRoot) { if(manager.isNestedConversation()) { manager.switchConversation(manager.getRootConversationId()); } } manager.endConversation(beforeRedirect); } ...
and adjust calls to endConversation(boolean beforeRedirect) accordingly.
This would allow you to specify @End(endRoot=true) on a method so the entire conversation stack is destroyed.
Any other thoughts? Thanks again for any help. -
2. Re: destroying the entire conversation stack through annotat
pmuir Aug 27, 2007 12:04 PM (in response to jacob.orshalick)You should do this in code as you currently are.
-
3. Re: destroying the entire conversation stack through annotat
jacob.orshalick Aug 27, 2007 12:08 PM (in response to jacob.orshalick)Okay, no problem. Was just curious if there was annotation based approach, or if this was potentially in the works. Thanks for the response.