Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Invalid
-
1.7.2
-
None
-
None
-
ALL
Description
We are attempting to passivate and activate GroupedConversationContext scoped beans across application server instances. Since the GroupedConversationContext scope is passivating we expected the state of the conversation to be persisted in a session offloaded store (redis) across different application server instances. The scenario here is such that if one app server instance dies the conversation carries on in the same browser tab from another app server that can activate the GroupedCoversationContext beans. This scenario does not work with Deltaspike. We expect a behavior to @SessionScoped beans.
Looking at the source code even though the GroupedConversationContext is a Passivating scope, DeltaSpike does not save the storageMap of Map<Object, ContextualInstanceInfo<?>> contextualInstances for the GroupedConversationContext to a HTTPSession. The passivation and activation of the contextual instances of the GroupedConversationContext beans does not rely on serialization/deserialization of session attributes.
We are using a very simple bean like so ...
@Named
@GroupedConversationScoped
public class BookingBean extends BaseBean
Is this a bug or working as designed or a feature?