> agreed, and i might be interested in contributing to this also. but that > depends on the stack you choose. i like spring+hibernate because it is more > lightweight and can run off jetty and spring provides a better ioc container > then ejb3 which might be important for autodiscovery/plugins architecture. > but this is just talk :) I'm familiar w/ Hibernate but unfortunately, know very little about Spring and know nothing about Jetty. I looked into Spring when I first started using Hibernate because I hated manually juggling the Hibernate Session/Transaction...apparently Spring has an elegant solution through templates? I was turned off by the amount of XML required in Spring (and Hibernate) and that's what drove me to appreciate EJB 3.0 - particularly JBoss.
Ivan has shown me how easy it is to develop a wicket app with the wicket+spring+hibernate stack and using jetty for debugging. It's very easy and very fast. The xml required for most tasks is pretty minimal. I'm not a huge fan of xml and would have never bought into spring if using it to manage hibernate required a lot.
Good luck with the portal. I'll keep a close eye on it.
-- Philip A. Chapman Desktop and Web Application Development: Java, .NET, PostgreSQL, MySQL, MSSQL Linux, Windows 2000, Windows XP |
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
