I am using EJB 3.0. So easy to work with. Toplink, GlassFish do everything. The ORM creates my tables from POJOs, transactions are a no-brainer. Comes with NetBeans out of the box. Why don't more users write about it?
Most of the time is spent on coding web pages (messy due to browser bugs and high user demands). Wicket is fun and easy. Business logic and all the persistence stuff are not issues that occupy my mind. What do you think about that? Bernard On Wed, 22 Jul 2009 18:40:19 -0700, you wrote: >Due to the fact that nearly every substantial sample Wicket app is >Spring-based, I imagine that there's something awesome about using Spring. >In fact, Wicket is what has finally gotten me to start learning Spring. > >I think I understand the basics of dependency injection -- configure your >objects in xml files and then inject them into your classes -- but I'm still >not clear on the advantage of it. I've read quite a ways into "Spring in >Action", and the author seems to assume that the reader will automatically >see why xml-based dependency injection is great thing. I must just be >missing something here. What I love about Wicket is being free from xml >files. Can anyone give me a concise explanation of how the advantages of >Spring are worth introducing a new layer into my applications? > >Dane --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
