JDev 11g: Best Practice Multi Field Validation / Reset in a Dialog Control

Question

I'm using JDev 11g and want to do the following (excuse my newbie learning curve):
1. Ability for the user to have a "dialog" form that they can edit their user information such as name, password, email, etc.
2. When user clicks OK want the system to validate that password fields are the same (there are two of them).
3. When user clicks Cancel I want the form to reset and the dialog to close.
Sounds easy right? However, I've seen several ways to implement and none of them seem straight forward and don't appear to work like I would want so instead spending the next day coding want to know if there's an easy solution.
For # 2:
The examples on the web use a phase listener for multi-form validation which when using a small dialog in a larger arena seems like overkill since the entire view will get my event right? Is there a similar thing for subform or subview?
Another example uses a listener for value change, however that doesn't work to well when trying to validate two fields match.
For # 3:
A standard OK Cancel dialog does not auto reset a form within it (it leaves the text - even invalid text in the field). Adding my own button for reset doesn't close the form and adding a reset listener doesn't close the form either. Is there a simple way and I'm just overlooking it? Should I use the standard buttons and somehow assign the cancel to reset the form or define my own and somehow close the popup? There's not too much documentation I can find about using Javascript to modify objects such as closing a dialog.
Anyone have the best approach that should be followed with less headache downstream and better portability to other forms with more complex validation? Any examples I missed that shows this working in a dialog?
Thank you,
Kris

Answer 1

Hi,
I don't understand #2, so ignoring it
#1 You can set the immediate property on the two password fields. In a value change listener you compare the two provided values and if they match, you continue processing. Otherwise you set an error message and call response complete. Note that as much as we like to provide everything declarative, coding is something that we cannot neglect completely in a programming environment.
#3 You can intercept the dialog close event and in this event determine which button was pressed. If it was the cancel button, get the current row from the underlying iterator and call refresh() passing one of the arguments you find when typing "Row." e.g DB refreshWithDBForget.
Frank