I suggest (tried and tested at my company) to use the Auth application as your base class and merge the spring related stuff into your subclass. The spring integration is agnostic for sessions and such, so you'll be up and running much quicker.
Personally I'm using the wicket.spring.SpringWebApplicationFactory mentioned in web.xml then and nice and cleanly inject my authentication strategy into my Application via normal spring IoC:
<bean id="wicketApplication" class="com.theoryinpractice.timetrackr.TimeTrackrApplication">
<property name="timeTrackrAuthorizationStrategy" ref="authorizationStrategy"/>
</bean>
<bean id="authorizationStrategy" class="com.theoryinpractice.timetrackr.TimeTrackrAuthorizationStrategy">
<property name="userManager" ref="userManager"/>
</bean>
The authorization strategy also has injected into it my hibernate DAO's so have full access to everything they need, cleanly and springy, without touching any of those odd little convience classes (actually I never knew they existed either).
Doing spring+wicket this way is much much nicer I find.
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
