myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Martin" <bal...@gmail.com>
Subject Re: SOS big problem with validation phase debugging
Date Tue, 06 Mar 2007 14:05:20 GMT
Thanks a lot Werner!! I am going to have a look at that.
J.

2007/3/6, Werner Punz <werner.punz@gmail.com>:
>
> Julien Martin schrieb:
> > Hello Werner,
> >
> > Thanks a lot for your reply!!!
> >
> > Can you please tell me how to do that??
> >
> >     Another way is to disable the validation programmatically
> >     via component bindings for the control at a certain usecase.
> >
> >
> > Can you direct me to snippets please?
> >
> > Julien.
> ok, this has been a long time, but I try to remember (dont beat me if i
> am wrong), first of all if you are not familiar with the component
> binding mechanism read it up, you basically can access your component tree
> from the backend
>
> binding="#{BannerPageBean.ticker}"
>
> secondly put an immediate="true" on your command link issuing the non
> validation case
>
> third access your component and disable the validation on it
> programmatically  (for instance ticker.setRequired(false))
>
> then either trigger the render phase directly (
> facesContext.renderResponse()) or let the flow do its work so that the
> validations needed still can do their work and other stuff might
> trigger...
>
>
> but, this is somewhat dirty, I really can recommend use the subforms
> nowadays, they are way cleaner.
>
> here is a good article on this issue:
>
> http://wiki.apache.org/myfaces/How_The_Immediate_Attribute_Works?highlight=%28immediate%29
>
>
>
>

Mime
View raw message