There are other WO developers better suited to answer those question. 
I'm cross posting to webobjects-talk and hope someone will pick up the 


Igor Vaynberg wrote:
> I guess i would be interested in knowing how web objects stores state 
> and how the back button is handled.
> is the state stored like tapestry - disjointed from the components?
> do components have to be beans?
> does it store undo history to handle the back button somewhere when the 
> state is stored serverside in session and not in urls?
> what drew me to wicket and away from tapestry were the following things:
> in wicket i could have very dynamic component hierarchies. i can take 
> any panel and switch it with any other panel, move components around, 
> etc. in tapestry the hierarchy is pretty much fixed from the creation of 
> the page because of how it defines, pools, and handles state.
> in wicket i can use good citizen pattern with constructors and have 
> private/protected final variables because wicket is unmanaged and so 
> components dont have to be beans. in tapestry components have to be 
> beans so none of these are possible. also to have your state persisted 
> you have to have your getters/setters abstract and declared (at least as 
> of a late 3.x).
> wicket keeps undo history so it can restore the proper state when the 
> back button is used. when you use tapestry you are pretty much on your 
> own when you use session scope.
> i tried to look for this stuff in wo docs but couldnt really find 
> anything useful.
> -Igor

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Wicket-user mailing list

Reply via email to