In what JSF phase does a transient CDI conversation get promoted to a long standing conversation. I am assuming that this happens in the invoke application phase since this is this is where the Conversation.begin() method can be called.

I am looking to implement a mechanism to start start conversations in the JSP phase listener. By configuring certain view ids as the starting point of a conversation (build on top of the ViewConfig in seam 3). So in the JSF listener i want to be able to check to see if a conversation needs to be started if current view id is the same as the configured view id. Kind of similar to conversation-begin tags within pages.xml - a feature that does not exist with seam 3.

Strike that. Looks like it should happen before the render response phase. would that be correct ? atleast looks like how that was handed in SEAM 2

ok i am not sure i understand. in CDI 1.1 i should be able to do this ?

Jason Porter wrote:

 

In CDI 1.1 I doubt you'd be able to do this in a portable fashion just because of how conversations were specified and implemented. CDI 1.1 should allow you to do this easily. For now, take a look at how things were done in the Seam Conversation module.

I dont see a converstion module in seam 3.

also if such a conversation management solutions built on top of the ViewConfig is not ok, then am i to believe that the only acceptable way to ever start conversations is explicity calling conversation.begin() wherever i expect a conversation to exist. which could be end being in several places.

Thanks. I am going to take a look at this.  but in the meanwhile I dont see any issues if I were to implement something like this

@LoggedIn

@FacesRedirect

@ViewPattern("/myApp/customer/*")

@AccessDeniedView("/public/login.xhtml")

@LoginView("/public/login.xhtml")

@BeginConversation

CUSTOMER_PAGES

And this is would basically take care of there being an conversation for any view id within /customer/*. Since there could be, in my case, several different ways to view any view within that url pattern. The @BeginConversation would be read during the @before RenderResponse phase in a phaseListener and start a conversation if there already did'nt exist one. Thoughts ?

we dont explicitly, in our case, end conversations. since the user can navigate to other apps and never come back. We do that by keeping a short time outs for conversations.