This examples project demonstrates two jdk 1.4 compliant ways to integrate wicket and spring.
direct approach
This is the simplest of approaches. All necessary spring beans are looked up via static lookups into the ExampleApplication class.
proxy approach
This approach wraps the static lookups for dependencies inside dynamic proxies. This allows the code to be decoupled from the application and easy to unit test.
jdk5 annotations approach
This approach allows us to annotate any component with SpringBean annotations, and have wicket initialize those fields with spring bean proxies