Agreed 100%
Eelco
Christopher Turner wrote:
My personal view is that we should not be including this as a standard feature of the core. It just adds extra jar dependencies, increases the size of the web application and so on. I'm personally more than happy with using the standard serialization mechanism provided by my application server vendor.
Serialzation is a messy thing to deal with and I think that a certain discipline and design ethic is forced on you by having to implement Serializable and deal with the differences between transient and persistent fields. If you want to design efficient web applications then you have to be aware of the issues involved in this. Wicket can hide it for simpler applications but as soon as you start growing to servers supporting session clustering and recovery then you have to understand a bit more about what is going on and make some important design decisions.
However, I would be +1 for providing XStreamPageState and other Xstream support as an optional implementation in the contrib package.
Regards, Chris
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
