RF 4 New ConversationScoped Stateful bean instance for each ajax request

bradleydouglas Aug 3, 2011 6:47 AM

Hi,

I've got a @ConversationScoped (long running cnversation) session bean that is backing page that has a rich:autocomplete and a a4j:ajax enable h:selectBooleanCheckbox on it.

Whenever I click on the checkbox or type a character in the autocomplete, I can see that a new instance of the stateful bean is created, and that the new conversation is started.

Can anyone give some suggestions as to how to fix or further diagnose this?

Thanks.

1. Re: RF 4 New ConversationScoped Stateful bean instance for each ajax request

blabno Aug 4, 2011 12:38 AM (in response to bradleydouglas)

This is a question for CDI forum.
Conversations are managed manually, so if you do not start it by hand it will not be long running (it will last only a single request).
Actions
2. Re: RF 4 New ConversationScoped Stateful bean instance for each ajax request

bradleydouglas Aug 4, 2011 6:38 AM (in response to blabno)

Thanks for the reply - you are right - it should have been in a CDI forum. I'm still getting across CSI & RF 4.

FWIW I was using a @PostConstruct initialisation method to create a long running conversation. However the conversation needs to exist before the h:form with the ajax enabled components on is rendered as this post explains: http://seamframework.org/Community/ConversationCreatedUntilPOST#comment128279

Thanks again.
Actions

Go to original post