Cs�k Norbert wrote:
Hi!
I think this is becase your backing beans are request scope. When you
display the second tab it is empty, because submitting the page with
the first tab doesn't set those values.
Yes that sounds reasonable they are indeed request scoped.
I think what we need is something, which is already in shale,
some kind of extended scope which is longer than request but shorter
than session.
(What shale does with dialogs)
You basically run into this problem every time you do something
which refreshes the page on the server in a dynamic way.
I've implemented a tab change eventlistener, which reloads the request
scope backing bean's data.
I worked around the problem yesterday night, by just implementing in
good ole javascript a few css tabs and a few divs which are triggered
and shown over javascript.
Works flawlessly.
