Dialog popup problem Jdev 10.1.3.1 ADF Faces

Question

I am having a problem with the behavior of my dialog popups, as follows:
1. The first time (in the first row) I click the CommandLink, the dialog popup opens and the display occurs. When I hit the close button on the dialog window, the return listener method in a request Scope managed bean fires.
2. I click on the Command Link in the second row. The dialog opens, again with the correct values being passed. This time, when I hit the Close button, the window closes, but the ReturnListener method does not execute.
3. Hit the command link in the third row. The link registers a click, but the popup does not appear.
Here is the Command Link:
<af:column sortProperty="Nsn" sortable="true"
headerText="#{bindings.CILOneProjROViewObj.labels.Nsn}">
<af:commandLink text="#{row.Nsn}" action="dialog:Nsn"
useWindow="true" windowHeight="200"
windowWidth="500" partialSubmit="true"
returnListener="#{project_go.resetProcessScope}"
immediate="false">
<af:setActionListener from="#{row.Nsn}"
to="#{processScope.holdNsn}"/>
<af:setActionListener from="#{row.Sos}"
to="#{processScope.holdIcp}"/>
<af:setActionListener from="#{'dialog:Nsn'}"
to="#{processScope.holdScreenName}"/>
</af:commandLink>
</af:column>
Here is the Close button on the popup:
<af:commandButton text="Close">
<af:returnActionListener/>
</af:commandButton>
And here is the bean method fired in the returnListener attribute above:
public void resetProcessScope(ReturnEvent returnEvent) {
// Add event code here...
AdfFacesContext adfctx = AdfFacesContext.getCurrentInstance();
String screenName = (String)adfctx.getProcessScope().get("holdScreenName");
System.out.println("screen:"+screenName+":"+adfctx.getProcessScope().get("holdNsn"));
if (screenName.equalsIgnoreCase("dialog:Nsn")) {
adfctx.getProcessScope().put("holdNsn",null);
System.out.println(adfctx.getProcessScope().get("holdNsn"));
adfctx.getProcessScope().put("holdScreenName",null);
I am absolutely stuck here. Is there a flag of some kind I'm missing?

Answer 1

I found an apparent resolution to the problem: I moved the storage of values from processScope to a sessionScope managed bean. Everywhere you see processScope in the code I provided, substitute sessionScope.bean.attribute.
Speculation: when a dialog window gets launched, it is being treated as a "separate process" with its' own processScope. Therefore, my changes weren't getting where they needed to be. However, that doesn't explain why setting a value in a setActionListener on the commandLink stored a value that the dialog could reference successfully. It also doesn't explain why the returnListener wasn't being fired every time.