Hi auron,
by chance I did the same on friday and it works for me. The only differences
to my xml-files I noticed was, as Igor said, the use of the wicket filter
instead of the wicket servlet. I.e.
<!-- tell wicket to retrieve the webapp class from the springwebappfactory
to enable DI in wicket-app class -->
<filter>
<filter-name>your.app.name</filter-name>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
<init-param>
<param-name>applicationFactoryClassName</param-name>
<param-value>org.apache.wicket.spring.SpringWebApplicationFactory</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</filter>
AND it is important to add a setter for the authentication manager (which is
not shown in the wiki), i.e.
public void setAuthenticationManager(AuthenticationManager
authenticationManager) {
_authenticationManager = authenticationManager;
}
otherwise spring wouldn't be able to inject the bean - this is different to
the annotation-based approach where a setter is not required. but AFAIK it
is not possible to inject a spring-bean into the application class using the
annotation based approach.
greetings
Michael
--
View this message in context:
http://www.nabble.com/spring-acegi-injection-question-tf4658329.html#a13338057
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
