Matthias Wessendorf schrieb:
On Mon, Apr 20, 2009 at 9:05 AM, Werner Punz <[email protected]> wrote:
Hia...
I sent a comment regarding this issue towards the given jcp-comments mail
address. Lets see what happens.
:-) /dev/null ?
That was mean :-)
I will also talk to Martin about it as you said, btw...
Another thing which really irks me generally. Since day zero about 90%
of the problems of the end users revolve around the fact that there is
no decent direct validation control for endusers within the spec.
We have immediate, which does not work out for many cases, since it just
shifts phases, we have
since jsf1.2 the possibility of adding alternate lifecycles which is
frankly spoken to complicated for many users and component sets add
subforms which also is outside of the spec but work out best so far
although they are still more complicated than a simple validation attribute!
An attribute in the command links or buttons with validation=true/false
would go a long way of removing a huge issue most users have with jsf.
(the other one the component api thankfully has been resolved)
I am glad Gerhard is adding something along those lines now to extVal,
but I think in the long run a simple attribute in the button or command
link which automatically turns off validation could help users
tremendously. I am not sure why this still has not made it into the spec.
Werner
