I thought on that once while I was designing the library. Since JSF is designed to support only server side validation, do we have to stick to the message components while validating at client side. That's open to discussion but I agree using message components to display client validation is more JSF like. Another advantage is that the user should choose both client-server validation and display both types of validation messages at same places. I will consider this when working on the new version.

regards,

Cagatay

On 4/17/06, Martin Marinschek <[EMAIL PROTECTED]> wrote:
Hmm....

you say the validation appears where the validation component is put -
what about the message components in JSF? In JSF, the validation
components don't output anything. They output their message via the
message tag. Shouldn't we do something similar on client-side?

regards,

Martin

On 4/17/06, Cagatay Civici <[EMAIL PROTECTED]> wrote:
> Ok Mike, then I am continuing the development at jsf-comp for now.
>
> Regards,
>
> Cagatay
>
>
> On 4/17/06, Mike Kienenberger < [EMAIL PROTECTED]> wrote:
> > On 4/17/06, Cagatay Civici < [EMAIL PROTECTED]> wrote:
> > > Yes, a jsf-comp release has more advantages if you compare it with a
> sandbox
> > > release. The disadvantage is that I can no longer impress people by
> saying
> > > that I have a component in myfaces for now:)
> > >
> > > Let me make a release at jsf-comp, then we will see what happens. By the
> way
> > > the library donation is currently in patch available state at jira, is
> it
> > > going to be canceled for now?
> >
> > Not unless you want it to be.   Nothing you do external to the MyFaces
> > project should affect what you're contributing to MyFaces.
> >
>
>


--

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Reply via email to