Ok thanks, I am currently thinking about another solution
to the problem which might make x:saveState and Serialisation
obsolete in the long run. Maybe I will find time after the 15th to
Sort of what shale does with their dialog system.
The idead would be to have some kind of scope tag
<x:scope value="scopeName" bean="beanName"/>
which puts a bean into a scope for as long as the scope is covered.
As soon as you hit a backend bean with a page outside of the scope
the scope bean is pushed from the session into a sessioned lastScope
variable, which is replaced as soon as the next scope runs out or maybe
at the time the next scope is triggered.
That would resolve following problems at once...
The problems of losing variables at the tabbing level (same goes for
The problem of having to traverse the fields, or to serialize the data
(which is a pain as well)
The problem of having as only solution of keeping variabls global for
certian periods of time, traversal or session holding.
I am not sure however if I can find the time to do this.
(I will donate my components from the last project however as soon as i
am finished here, got the ok from the management yesterday)
Shale does basically the same on framework level with their dialog
system (it does much more, but that one is the most important stuff
IMHO). But that one in my opinion is a good extension on the framework
level and harder to grasp.
Enrique Medina wrote:
Yes, you have to ;-)
On 5/28/05, Werner Punz wrote: