Details
Description
For ICEfaces 2.0 Sparkle components we require a successor to the ICEfaces 1.8 components "partialSubmit" feature to allow ease of validation and processing of form elements as they are entered by the user.
Current thinking is to have a "partialSubmit/singleSubmit/autoSubmit" boolean attribute on each input component. When set to 'true', a value change on that component would submit the form that the component resides in with the equivalent of an f:ajax "execute=this, render=all".
The intention is to have validation and processing be performed on that input component alone, while rendering the whole component tree so that any other components who's state's may change as a result of the value change on the component (e.g. message component) are rendered.
It is not clear at this time of this alone will be sufficient, as there is a concern that any validation error messages from previous autoSubmits may be lost when a subsequent autoSubmit occurs on a different component, as even though the original component may remain in an invalid state, without being executed no events would fire to populate the messages components, etc. It may be necessary to also provide an enhanced version of the messages components that would cache previous messages and remove them if the source component was either no longer in the component tree, there but not rendered, or no longer invalid.
Current thinking is to have a "partialSubmit/singleSubmit/autoSubmit" boolean attribute on each input component. When set to 'true', a value change on that component would submit the form that the component resides in with the equivalent of an f:ajax "execute=this, render=all".
The intention is to have validation and processing be performed on that input component alone, while rendering the whole component tree so that any other components who's state's may change as a result of the value change on the component (e.g. message component) are rendered.
It is not clear at this time of this alone will be sufficient, as there is a concern that any validation error messages from previous autoSubmits may be lost when a subsequent autoSubmit occurs on a different component, as even though the original component may remain in an invalid state, without being executed no events would fire to populate the messages components, etc. It may be necessary to also provide an enhanced version of the messages components that would cache previous messages and remove them if the source component was either no longer in the component tree, there but not rendered, or no longer invalid.
attached test app...
This is the current bahavior...