ADF Dialog Framework Cancel Button

Question

Hi all,
We're experiencing, in multiple applications, a problem with a Cancel button (immediate="true") on a page launched by the dialog framework. While the value does not change in the model layer (saving to the database confirms this), it does seem to appear in the application UI, even after clicking the cancel button, until you post data.
Details follow:
This code is all JHS-generated, but we've spoken to Steven Davelaar, and he's pretty sure it's not a JHS problem. I certainly can't see anything obviously wrong with the code.
Here's the component that launches the dialog, minus attributes like "rows" and "columns":
<af:panelLabelAndMessage label="MIS Notes: "
    id="RpReportDocHeaderVwMisNotesLabel">
    <af:inputText id="SomeAttr" value="#{bindings.SomeAttr.inputValue}"
        required="#{bindings.SomeAttr.mandatory}"
        simple="true" partialTriggers="SomeAttrEditorLink"
        binding="#{SomeAttrEditorItem.editorItem}">
    </af:inputText> 
    <f:facet name="end">
        <af:commandLink id="SomeAttrEditorLink"
            action="dialog:editor" immediate="true" useWindow="true"                           
            partialSubmit="true" windowHeight="320" windowWidth="670"
            returnListener="#{SomeAttrEditorItem.returnedFromEditor}"
            launchListener="#{SomeAttrEditorItem.launchEditor}">
            <af:objectImage source="/jheadstart/images/editor.gif"/>
        </af:commandLink>
    </f:facet>
</af:panelLabelAndMessage />The editor window, minus layout, form, etc. elements, is as follows:
<af:inputText rows="10" columns="100"
    value="#{processScope.editorValue}"
    maximumLength=
        "#{processScope.editorMaxLength==0 ? null : processScope.editorMaxLength}" />
<af:panelButtonBar>
    <af:commandButton text="Cancel" immediate="true">
        <af:returnActionListener/>
    </af:commandButton>
    <af:commandButton text="OK">
        <af:returnActionListener value="#{processScope.editorValue}"/>
    </af:commandButton>
</af:panelButtonBar>Now, SomeAttrEditorItem is a managed bean of type oracle.jheadstart.controller.jsf.bean.EditorItemBean, so it's JHS code, but nothing about it should really matter if the returnActionListener for the Cancel button doesn't contain a value and is immediate, should it?
Any help much appreciated. Thanks much,
Avrom

Answer 1

Thanks, Frank. This looks like a JHS bug (albeit one we can work around by writing our own template)--JHS should probably not be generating code that leaves cancelled changes in place. I'll notify them on their forum.
[Edit:] Actually, there's something I don't understand about the instructions. In a case like this, I really only want to undo changes to a particular attribute--whatever attribute the dialog changed. And ideally, I don't want to refresh to the last pre-commit point; I want to just discard the changes that were made by this particular dialog. So I don't really think Row.refresh() is going to work here.
Now, I could do something like this: In the launch listener, store the relevant attribute in some transient location, and on return, refresh it. But that seems overly complicated; isn't there a way to just not submit a dialog's values upon returning to the original form, or, at least, to prevent them from updating the model?
Message was edited by:
Avrom
[Further edit:] Wait, no, there's something even stranger going on here. Note that the text input in the dialog isn't bound to "#{bindings.SomeAttr.inputValue}"; it's bound to "#{processScope.editorValue}". And the cancel button doesn't even have a returnActionListener! So how is the value getting passed back to the original form?
Message was edited by:
Avrom