I wonder whether it would be possible to define a form "inside" each tab
to
force a "partial" submit.
It just raises the question, whether the tabbed pane automatically adds
a 
form around the complete tab-widget, or just on the clickable tabs,...

>From the usability I would argument, that the click on the tab
automatically should throw away the form-content on the tab, because it
is not a form-related button (which should be below the input-fields).
And
ALL links (which includes the tabs outside the input-form) should be
considered as
form-unfriendly navigation => not submitting the form... This would also
make it 
possible to get rid of the Javascript on each link (no need to submit a
form).

regards
Alexander 

-----Original Message-----
From: Alexander Wallace [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 05, 2007 11:08 PM
To: MyFaces Discussion
Subject: Re: why tab pane submits/validates all tabs

Ok... i guess that's then the expected behavior, just not what I  
expected...

thanks!

On Jun 5, 2007, at 3:37 PM, Jesse Alexander ((KSFD 121)) wrote:

> well the tabbedPane always renders all components but just displays
> only one tab. As it uses links it needs the form around the whole and
> submits it in one piece...
>
> hth
> Alexander
>
> -----Original Message-----
> From: Alexander Wallace [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 05, 2007 10:26 PM
> To: MyFaces Discussion
> Subject: Re: why tab pane submits/validates all tabs
>
> I guess you meant server side tab switch... i tried that, but when I
> use it, the action or action listener methods are never visited when
> buttons are clicked... it is very messed up...
>
> thanks!
>
> On Jun 5, 2007, at 1:01 PM, Alexander Wallace wrote:
>
>> I'm using server side... But still get the undesired result...
>>
>> Any clues?
>>
>> On Jun 5, 2007, at 12:35 PM, Mike Kienenberger wrote:
>>
>>> It's been awhile since I used tabs, but I think if you use server-
>>> side
>>> tab switching, only the current tab will be rendered (and submitted
>>> and validated).
>>>
>>> If you use client-side tab switching, all tabs are rendered (but
>>> hidden with javascript) and all tabs are submitted.
>>>
>>> On 6/5/07, Alexander Wallace <[EMAIL PROTECTED]> wrote:
>>>> I have a MyFaces portlet with 5 or so tabs, each with its own  
>>>> set of
>>>> independent (i would hope) fields and submit buttons... However,  
>>>> all
>>>> elements in all tabs are submitted and validated when either of  
>>>> tabs
>>>> has a submit button clicked...
>>>>
>>>> Is this really how it is supposed to be? I'm using MyFaces 114
>>>>
>>>> Thanks!
>>>>
>>>>
>>>
>>
>>
>
>

Reply via email to