hi avinash,

dswid is the window-id -> it just needs to be unique across browser
windows/tabs.
(the window-context is like a flexible session per browser windows/tabs
which can contain multiple conversations/conversation-groups, ...)
-> closing one sub-group, will never lead to a new dswid.
(it just drops the instances bound to that group and for sure just for the
current window-context and not all window-contexts.)

regards,
gerhard

http://www.irian.at

Your JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German

Professional Support for Apache
MyFaces, DeltaSpike and OpenWebBeans



2017-04-11 22:44 GMT+02:00 Avinash Moram <[email protected]>:

> Hi,
>
> I have implemented nested conversations using the Implicit Sub Groups
> method. Now I am trying to close the sub group, everything seems to be
> working fine except that I still see the old dswid in the address bar url.
> I am sure the current EJB (which is in parent group) which calls the
> conversationManager.closeConversationGroup doesn't have any references of
> the other ejb's from the sub group.
>
> Is there something I am missing that needs to be done other than closing
> the subgroup?
>
> And also, every ejb which has different jsf pages shows the same dswid, is
> it because all these ejb's belong to the same group? I traverse through one
> ejb through another either using links or buttons which call the ejb method
> on action attribute of that link or button to return a view.
>
> @ConversationGroup("GroupParent") // view - home.xhtml -- same dswid
> ParentEJB (I am closing the subgroup "SubGroupParent" here)
>
> @ConversationSubGroup(of = GroupParent.class, subGroup = SubGroup1.class)
> public class ConversationWQImplicitSubGroup
>
> @ConversationSubGroup(of = SubGroup1.class, subGroup =
> SubGroupParent.class)
> public class ConversationWQSearchImplicitSubGroup
>
> @ConversationGroup("SubGroup1")
> ChildEJB1 implements SubGroupParent
>
> @ConversationGroup("SubGroup1")
> ChildEJB2 implements SubGroupParent
>
>
>
> Thanks & Regards,
> Avinash
>

Reply via email to