This content has been marked as final.
Show 3 replies
-
1. Re: tabPanel Issue
nbelaevski Apr 29, 2009 10:40 AM (in response to cg1)Hello Ganesh,
a4j:include creates components tree for all tabs, not just for the one being rendered. You can work around that by making dynamic viewId:viewId="#{bean.viewId}"
and refer to the blank views for tabs that are not the current one. -
2. Re: tabPanel Issue
cg1 Apr 30, 2009 7:26 PM (in response to cg1)Thanks for this response...
But at some point if the user clicks the second tab, then viewId of first tab will have to be reset. This means if the user clicks the first tab after clicking the other tabs, data will have to be refetched.
Is there no other way to have dynamic tab content?
Thanks
Ganesh -
3. Re: tabPanel Issue
nbelaevski Apr 30, 2009 7:39 PM (in response to cg1)You can make client-mode tabs empty by default and use a4j:support that will track tabs switches and load data.