On 8/9/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> > Although access to the other components by navigating the component
> > tree is guaranteed to work, I take your point that it makes the logic
> > of this "check" type validator more fragile. Here's a technique to
> > consider that might alle
> Although access to the other components by navigating the component
> tree is guaranteed to work, I take your point that it makes the logic
> of this "check" type validator more fragile. Here's a technique to
> consider that might alleviate the issue somewhat:
Yes that was my point. Wouldn't y
On 8/8/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> I have another possible solution for this validation problem. It
> involves going back to your original answer where you suggested the
> Process Validations phase as the logical place for this type of
> activity to occur.
>
> My main problem
I have another possible solution for this validation problem. It
involves going back to your original answer where you suggested the
Process Validations phase as the logical place for this type of
activity to occur.
My main problem was access to other components so I could see their
submitted val
> I'm sure this is obvious to you :-), but to help the rest of us out
> ... can you provide a concise statement of what this method would be
> used for? Let's assume we use the name check() or whatever you want
> ... what would the Javadocs say?
This method allows for the option to perform compl
On 8/8/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> [Sorry I replied to the user's list by mistake. This is a repost to
> the dev list.]
>
> Craig,
>
> I have been thinking about this issue some more and I have some
> additional thoughts in response to your comments.
>
> I definitely like th
[Sorry I replied to the user's list by mistake. This is a repost to
the dev list.]
Craig,
I have been thinking about this issue some more and I have some
additional thoughts in response to your comments.
I definitely like the idea of a new method in ViewController. I
wouldn't call it validate
> With a bit of effort, you can gain access to the *submitted* values of
> other components (because the validator receives a reference to the
> component being validated and the FacesContext, so you can navigate
> around the tree) ... but, your fundamental issue is that Process
> Validations happe
On 8/2/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> We're having some difficulties writing complex validators in JSF. In
> many cases we have a field whose validation depends on the value of
> another field. JSF doesn't really handle this situation very well in
> the processValidations phase b
We're having some difficulties writing complex validators in JSF. In
many cases we have a field whose validation depends on the value of
another field. JSF doesn't really handle this situation very well in
the processValidations phase because you don't have access to the
other values.
I've run i
10 matches
Mail list logo
