Spring gives flexibility in your services layer (whatever you call it).
Making things transactional, adding memoization, talking to remote
interfaces, configuring Hibernate and JMX beans, all that kind of stuff is
easy with Spring and often unbelievably hard without.
As said, Spring has no value in a Wicket application with the exception of
calling out to the service layer. This is where the @SpringBean comes in
handy.
Regards,
Erik.
On Wed, 22 Jul 2009 18:40:19 -0700, Dane Laverty <danelave...@gmail.com>
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
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
