You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Mike Kienenberger <mk...@gmail.com> on 2006/02/08 19:02:21 UTC
status of the optional validator stuff [Was: Bookmarking, History and JSF]
On 1/31/06, Martin Marinschek <ma...@gmail.com> wrote:
> By the way - any update on the optional validator stuff together with
> partial validation? Ok, maybe we should start a different thread on
> this ;)
I finally got around to updating the wiki page.
The short answer is that it works fine as long as you're also using
facelets. It should also work if you're using JSF 1.2. It can't
work with standard JSF 1.1 component tree building rules.
=================================================
Known issues
* JSF 1.1 recreates validators and converters each request. This
makes it difficult (maybe impossible) to implement a validator element
that wraps other validator elements. Thus, you must also use facelets
with JSF 1.1 in order to use the optional validation framework.
Fwd: status of the optional validator stuff [Was: Bookmarking, History and JSF]
Posted by Martin Marinschek <ma...@gmail.com>.
---------- Forwarded message ----------
From: Martin Marinschek <ma...@gmail.com>
Date: Feb 8, 2006 11:07 PM
Subject: Re: status of the optional validator stuff [Was: Bookmarking,
History and JSF]
To: Mike Kienenberger <mk...@gmail.com>
You're sure there are any API changes?
If there aren't, we might get through...
Why do we need special tree-building for this? That's in fact just
like creating child-components, right?
regards,
Martin
On 2/8/06, Mike Kienenberger <mk...@gmail.com> wrote:
> I don't know, but I suspect it'd break the TCK. 1.2 corrected the
> 1.1 design flaw, so I'm guessing it's required in 1.1.
>
> On 2/8/06, Martin Marinschek <ma...@gmail.com> wrote:
> > Does it require API changes or would it break the TCK if we would go
> > "1.2" compatible here?
> >
> > regards,
> >
> > Martin
> >
> > On 2/8/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > On 1/31/06, Martin Marinschek <ma...@gmail.com> wrote:
> > > > By the way - any update on the optional validator stuff together with
> > > > partial validation? Ok, maybe we should start a different thread on
> > > > this ;)
> > >
> > > I finally got around to updating the wiki page.
> > >
> > > The short answer is that it works fine as long as you're also using
> > > facelets. It should also work if you're using JSF 1.2. It can't
> > > work with standard JSF 1.1 component tree building rules.
> > >
> > > =================================================
> > > Known issues
> > >
> > > * JSF 1.1 recreates validators and converters each request. This
> > > makes it difficult (maybe impossible) to implement a validator element
> > > that wraps other validator elements. Thus, you must also use facelets
> > > with JSF 1.1 in order to use the optional validation framework.
> > >
> >
> >
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: status of the optional validator stuff [Was: Bookmarking, History and JSF]
Posted by Martin Marinschek <ma...@gmail.com>.
I wonder where that is.
If I look into UIInput, it calls in restoreState/saveState
saveAttachedState on the validators.
Now that should save and restore the state of the validators, right?
Maybe there's something in the tag which kills them again.
regards,
Martin
On 2/8/06, Mike Kienenberger <mk...@gmail.com> wrote:
> I'm looking through the JSF 1.1 spec.
> I don't actually see where validators get recreated rather than
> restored. In fact the spec seems to indicate the opposite. Yet,
> that's the behavior.
> I'm also looking through myfaces api, and again I can't see where it's
> happening, but it's happening somewhere.
>
> On 2/8/06, Martin Marinschek <ma...@gmail.com> wrote:
> > You're sure there are any API changes?
> >
> > If there aren't, we might get through...
> >
> > Why do we need special tree-building for this? That's in fact just
> > like creating child-components, right?
> >
> > regards,
> >
> > Martin
> >
> > On 2/8/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > I don't know, but I suspect it'd break the TCK. 1.2 corrected the
> > > 1.1 design flaw, so I'm guessing it's required in 1.1.
> > >
> > > On 2/8/06, Martin Marinschek <ma...@gmail.com> wrote:
> > > > Does it require API changes or would it break the TCK if we would go
> > > > "1.2" compatible here?
> > > >
> > > > regards,
> > > >
> > > > Martin
> > > >
> > > > On 2/8/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > > > On 1/31/06, Martin Marinschek <ma...@gmail.com> wrote:
> > > > > > By the way - any update on the optional validator stuff together with
> > > > > > partial validation? Ok, maybe we should start a different thread on
> > > > > > this ;)
> > > > >
> > > > > I finally got around to updating the wiki page.
> > > > >
> > > > > The short answer is that it works fine as long as you're also using
> > > > > facelets. It should also work if you're using JSF 1.2. It can't
> > > > > work with standard JSF 1.1 component tree building rules.
> > > > >
> > > > > =================================================
> > > > > Known issues
> > > > >
> > > > > * JSF 1.1 recreates validators and converters each request. This
> > > > > makes it difficult (maybe impossible) to implement a validator element
> > > > > that wraps other validator elements. Thus, you must also use facelets
> > > > > with JSF 1.1 in order to use the optional validation framework.
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > http://www.irian.at
> > > >
> > > > Your JSF powerhouse -
> > > > JSF Consulting, Development and
> > > > Courses in English and German
> > > >
> > > > Professional Support for Apache MyFaces
> > > >
> > >
> > >
> >
> >
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: status of the optional validator stuff [Was: Bookmarking, History and JSF]
Posted by Mike Kienenberger <mk...@gmail.com>.
I don't know, but I suspect it'd break the TCK. 1.2 corrected the
1.1 design flaw, so I'm guessing it's required in 1.1.
On 2/8/06, Martin Marinschek <ma...@gmail.com> wrote:
> Does it require API changes or would it break the TCK if we would go
> "1.2" compatible here?
>
> regards,
>
> Martin
>
> On 2/8/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > On 1/31/06, Martin Marinschek <ma...@gmail.com> wrote:
> > > By the way - any update on the optional validator stuff together with
> > > partial validation? Ok, maybe we should start a different thread on
> > > this ;)
> >
> > I finally got around to updating the wiki page.
> >
> > The short answer is that it works fine as long as you're also using
> > facelets. It should also work if you're using JSF 1.2. It can't
> > work with standard JSF 1.1 component tree building rules.
> >
> > =================================================
> > Known issues
> >
> > * JSF 1.1 recreates validators and converters each request. This
> > makes it difficult (maybe impossible) to implement a validator element
> > that wraps other validator elements. Thus, you must also use facelets
> > with JSF 1.1 in order to use the optional validation framework.
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
Re: status of the optional validator stuff [Was: Bookmarking, History and JSF]
Posted by Martin Marinschek <ma...@gmail.com>.
Does it require API changes or would it break the TCK if we would go
"1.2" compatible here?
regards,
Martin
On 2/8/06, Mike Kienenberger <mk...@gmail.com> wrote:
> On 1/31/06, Martin Marinschek <ma...@gmail.com> wrote:
> > By the way - any update on the optional validator stuff together with
> > partial validation? Ok, maybe we should start a different thread on
> > this ;)
>
> I finally got around to updating the wiki page.
>
> The short answer is that it works fine as long as you're also using
> facelets. It should also work if you're using JSF 1.2. It can't
> work with standard JSF 1.1 component tree building rules.
>
> =================================================
> Known issues
>
> * JSF 1.1 recreates validators and converters each request. This
> makes it difficult (maybe impossible) to implement a validator element
> that wraps other validator elements. Thus, you must also use facelets
> with JSF 1.1 in order to use the optional validation framework.
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces