I found out about Wicket at the web framework smackdown at JavaOne. I've been poking around the documentation and mailing list since then, but I'm truly evaluating Wicket this week. I've customized a couple of the examples and like what I see so far very much!
Spring integration is a requirement for me and the company I work for. Were using Hibernate and injecting the DAO's into services (business logic) layer. We use Spring MVC and the services are injected into the Spring MVC controllers. I'm trying to figure out what I would inject the services into within the wild Wicket world. Any suggestions? I've been thinking that I would inject the services into the Page's and just create a SpringPageFactory. That seams easy enough, but the part that is troubling me is "there is a big problem with injection. Pages get serialized." Now I need to learn more about Wicket to find out why pages are being serialized. More importan, what is doing the deserialization? What would it take to reinject those services when the pages are deserialized? I've worked with Spring quite a bit and can probably help out on that front, but I just need to learn more about Wicket in order to contribute. Cameron ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
