Dane Laverty 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
You dont have to use spring with wicket. Spring is a business layer
framework essentially. It gives you so much convenience to decouple
services from its clients. I tried to use it to manage all the web
components, then I realized that doesnt give me much at all. Sometimes,
a simple "new Page("id")" is just a better solution.
But I do encourage you to learn spring, especially if you value
automated tests. I cannot live with it now.
Jas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
