When I did my Spring web applications, I split Spring context files into a few
smaller ones (example: one for web beans, one for DAO beans, one for Service
beans, etc).
I would like to follow the same approach in my Wicket application, but I notice
a few odd things:
1. The order of these Context files in web.xml plays a role. If not right,
Tomcat will not start and report wicket "WebApplication" cannot be found.
2. Service beans specified through the following:
@SpringBean
private SupportService supportService;
result in runtime error that the bean of type SuppportService cannot be found
if a service bean is specified in a different context file other than that of
wicket "WebApplication".
Any of you had similar experience. Any fix?
Regards.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
