-
1. Re: rich tab's resets
moldovan Aug 24, 2007 8:14 AM (in response to tkalactomo)It ist normal, that the first Tab gets opened again, when you do a full page submit!
Attribute selectedTab of TabPanel can be usefull for you! -
2. Re: rich tab's resets
lbbishop Aug 24, 2007 10:50 AM (in response to tkalactomo)The selected tab can be controlled programmatically via the rich:tabPanel selectedTab attribute.
-
3. Re: rich tab's resets
tkalactomo Aug 27, 2007 2:53 AM (in response to tkalactomo)Thanks for the reply!!
Ok I guess for the switch type client this would be a normal behaviour,
but why other two(server and ajax) doesn't somehow save state of the component??This isn't such a problem do get it work the way you
just described but I still think that this should be done by the side of the
component! -
4. Re: rich tab's resets
tkalactomo Aug 27, 2007 9:16 AM (in response to tkalactomo)"tkalactomo" wrote:
Thanks for the reply!!
Ok I guess for the switch type client this would be a normal behaviour,
but why other two(server and ajax) doesn't somehow save state of the component??This isn't such a problem do get it work the way you
just described but I still think that this should be done by the side of the
component!
Can some of the developers tell the answer?
Thanks in advance -
5. Re: rich tab's resets
ilya_shaikovsky Aug 27, 2007 9:51 AM (in response to tkalactomo)We think the component must not always remember its state. Thats why we provide selectedTab and if you need you may save state from your model.
-
6. Re: rich tab's resets
tkalactomo Aug 28, 2007 2:30 AM (in response to tkalactomo)"ilya_shaikovsky" wrote:
We think the component must not always remember its state. Thats why we provide selectedTab and if you need you may save state from your model.
Ok i agree solution is good but not the best,if you don't mind.
Component <rich:tab>when used on the page has always
multiple tabs.So logic from my point of view would be that
component "must not always lose it's state".
So can there be some attribute that would control
the behaviour of state saving.Example "save-state=true/false".
Thanks in advance -
7. Re: rich tab's resets
tkalactomo Aug 28, 2007 3:20 PM (in response to tkalactomo)
Ok i agree solution is good but not the best,if you don't mind.
Component <rich:tab>when used on the page has always
multiple tabs.So logic from my point of view would be that
component "must not always lose it's state".
So can there be some attribute that would control
the behaviour of state saving.Example "save-state=true/false".
Please ilya_shaikovsky,who answered on my subject, or some of the developers,
can you answer please on my question? -
8. Re: rich tab's resets
ishabalov Aug 28, 2007 4:52 PM (in response to tkalactomo)Dear ttkalac!
Please provide us with some additional details:
1. What is exact question you want us to answer?
2. What was the problem that you had?
Thank you,
Igor. -
9. Re: rich tab's resets
tkalactomo Aug 29, 2007 2:32 AM (in response to tkalactomo)"ishabalov" wrote:
Dear ttkalac!
Please provide us with some additional details:
1. What is exact question you want us to answer?
2. What was the problem that you had?
Thank you,
Igor.
Hy!
Here are the answers on your question Igor.
Component we are discussing is Tab panel.
1.Can there be some attribute to determine the state saving of the
component (example: "save-state=true/false")??This will avoid the
unnecessary code in the backing bean for the component state saving
and present us the simplicity of using that component.
2.My exact problem is that the component tab panel loses is state
when used with multiple tabs(That component is always used with multiple tabs).
Example when I am on second tab
and make the submit(server submit)
on that tab/page component loses its state
and switches to first.This is really frustrating because of that.
So I again must tell...I really think that this can be done to avoid unnecessary code
and provide us simplicity,and all benefits that richfaces
carry within. -
10. Re: rich tab's resets
tkalactomo Aug 30, 2007 2:27 AM (in response to tkalactomo)I don't wont to be annoying...
Please answer!