Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
From: Peter Rawlins <peter.rawlins@focus-solutions.co.uk>
To: MyFaces Discussion <users@myfaces.apache.org>
Date: Fri, 20 Jul 2007 16:57:45 +0100
Subject: RE: [Trinidad] panelTabbed - validation of unvisited tabs
Thread-Topic: [Trinidad] panelTabbed - validation of unvisited tabs
Thread-Index: AcfKIQXI4gHw6xhFRPi2H+WvUTGJRQAwGi3w
Message-ID: 
 <BCA3CD31FF199F4AA8361A21286176572CC6C04FDB@exchange.focus-internal.co.uk>
References: 
 <BCA3CD31FF199F4AA8361A21286176572CC6C04A3A@exchange.focus-internal.co.uk>
 <6dac79b90707190922h4a408fafp729b2e62ee70b776@mail.gmail.com>
In-Reply-To: <6dac79b90707190922h4a408fafp729b2e62ee70b776@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 7/19/07, Adam Winer wrote:
>
> There's two questions here:
> (1) Is there a way to validate tabs that have been disclosed,
>   but aren't disclosed right now?
> (2) Is there a way to validate tabs that have never been disclosed.
>
> For 1, the answer is yes:  call processValidators() and
> processUpdateModel() on the children of the showDetailItem.
>
> For 2, the answer is no, you can't.  And you can't set the submitted valu=
e to "", because > that'll blow up for many renderers.
>
> What you need here is bean-level validation, not component-level validati=
on.
> Alternatively, you might disable the button until all tabs have been visi=
ted.


Adam,  thanks for the quick reply.

I've got quite a lot of similar pages to create using tabbedPanels, so I'd =
like to make the most of the automatic validation based on the declarative =
page definition.

After careful consideration, I've decided to go with your very last suggest=
ion - with a slight tweak :-)

I plan to track which tabs have been visited, but leave the button always e=
nabled.
When the button is pushed, the action will first perform a check that all n=
ecessary tabs have been visited, and if not, disclose the next required tab=
 as appropriate.  If the check passes, then the normal button action will b=
e performed.  I'll be relying on the standard behaviour of not letting the =
user get out of the current tab unless it's valid - so I need to ensure tha=
t no "immediate" actions switch away from the current tab.

Additionally, I expect to use bean-level validation for cross-field validat=
ion where the fields are on different tabs.

Many thanks for your help.

Regards,
Peter.