Hibernate 3 is neat. I just started a new (hobby) project using it with annotations. I hate the fact that they changed the package names though, I'll probably remove the Hibernate part of wicket-contrib because of this.
Eelco
go smack in the face of Wicket's goals of focusing on ease of use before performance. No "discipline" is lost whether you use standard serialization or XStream. The same persistance rules apply (transient keyword, etc) whether you use one or the other. All we're doing is making it *easier* to serialize and if users want to come back and fine-tune the process further they can still do so. I think you guys are assuming (incorrectly) that XStream is "unstable magic" and that its performance is bad. Neither is true.
I have compared XStream vs Serialization to Java vs C before. I honestly think it's that sort of thing.
And Eelco, I'll work on the plugin as soon as I get around to working with Wicket again. Right now I'm knee-deep migrating to Hibernate3.
------------------------------------------------------- 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
