You could use the @Autowired Spring annotation and the
autowire="byType" attribute to the bean definition to support autowiring
to get the same effect as @SpringBean brings in Components.
e.g.
<bean class="foo.bar.MyApplication" autowire="byType" />
Regards,
Mike
I was always thinking that the @SpringBean annotation should be used in
Pages and/or components.
You should inject your dependencies in your Application directly in your
spring.xml.
your spring.xml should contain something like this:
<bean class="foo.bar.MyApplication">
<property name="googleMapsKey" value="${googlemaps.key}"/>
<property name="myService" ref="service"/>
</bean>
your web.xml contains then a reference to your Application bean
<filter>
<filter-name>wicket.fast-web</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>
</filter>
On Wed, Oct 28, 2009 at 9:22 PM, Steve Hiller <sh...@bellsouth.net> wrote:
Hi All,
Are there any issues associated with using the @SpringBean annotation in a
class that
inherits from WebApplication or AuthenticatedWebApplication?
Thanks,
Steve
