1 of 1 people found this helpful
Manish Prajapati wrote:
above discussion tell many things about seam 2 to seam 3 migration .
still what to do with following ????
1. synchronized annotation from seam 2 ----
I can't really think of a need for this in CDI / Seam 3
2. classes extending seamListener
Um, my best idea is to create a new @ApplicationScoped bean and use @PreDestory, or create a CDI extension and listen to the BeforeShutdown event and the AfterDeploymentValidation event. That's actually probably the best.
Create a ServletRequestListener.
4. Conversation.isnested() , conversation.getviewId()
isNested - Seam3 doesn't have nested conversations
getViewId - Pull that from the FacesContext
these changes are like hurdles ,what to do ?????
I don't recall off the top of my head, but I think there's something in Seam Faces.
i would really appreciate any suggestion , anything on above .
hi jason ,
in seam 3 if i want to skip a page so do we have UIAction or UIConversationId here like seam 2 ?????
i can't see one , or jsf2 provide something similar ???