Jurgen Lust schrieb:
> I have checked the conversation context feature in this case: the
> parameter is sent with every ajax request. For example, the
> 'last'-button in the scroller contains this javascript:
>
> onclick="A4J.AJAX.Submit('_viewRoot','j_id7',event,{'ignoreDupResponses':true,'parameters':{'j_id7:personTableModel:j_id19':'last'}
> ,'eventsQueue':'j_id7:personTableModel:j_id19','actionUrl':'/3column.jsf?javax.portlet.faces.DirectLink=true&conversationContext=2'}
> ); return false;
>
> But as I said in my first mail, it does not seem to work.
>
Isn't the problem that you have one window in which this URL is being
used (conversationContext=2), and then in a different window something
also uses (conversationContext=2) and then the two windows interact?
When the conversationContext is the same, then of course they will. The
windows will only be isolated if the conversationContext value is
*different* for each window.
> On the same page, there is an a4j:commandButton which contains a
> similar javascript, and that button does work correctly in 2 parallel
> windows, and 2 different conversations.
>
> onclick="A4J.AJAX.Submit('_viewRoot','j_id27',event,{'parameters':{'j_id27:j_id30':'j_id27:j_id30'}
> ,'actionUrl':'/3column.jsf?javax.portlet.faces.DirectLink=true&conversationContext=2'}
> );return false;"
>
Really?
So this button has some effect on the server that *would* be observable
in your second window if they were referencing the same bean instance on
the server, but you do NOT see any change in your second window after
the button is clicked?
I would be very surprised...
Regards, Simon
