[
https://issues.apache.org/struts/browse/SHALE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43722#action_43722
]
Gary VanMatre commented on SHALE-356:
-------------------------------------
I think we will need the full client id of the associated parent component to
pass on to the message handler callback. The full client id will allow finding
the node by id. Then, a popup-layered div can be aligned to the element. That
would be one method for displaying validation messages. Another approach that
AJAX JSF libraries like ADF Rich Faces takes it that they display an inline
dialog that looks like an external browser window. All the error messages are
displayed in the dialog that can be moved around on the page using
drag-and-drop. Clicking on an error within the error dialog sets focus to that
component within the page. Not sure if we want to try to build something like
this or just provide a callback that can utilize existing JS frameworks.
> Make it possible to report client side validation errors via DHTML
> manipulations on message elements
> ----------------------------------------------------------------------------------------------------
>
> Key: SHALE-356
> URL: https://issues.apache.org/struts/browse/SHALE-356
> Project: Shale
> Issue Type: Improvement
> Components: Validator
> Reporter: Craig McClanahan
> Fix For: TBD
>
>
> Currently, the Shale Validator implementation reports client side validation
> errors the way that was also used in Struts -- a pop-up alert box. It would
> be very useful to be able, instead, to use DHTML manipulation on the client
> side to update an <h:message> component relevant to the input component(s) in
> error, and/or an <h:messages> component to capture all messages.
> This is likely to depend on some refactoring of the javascript methods
> provided by Commons Validator 1.3.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
