Hi,
I have done some work to locate the Spring application context in
another way. Both wicket-spring and wicket-spring-annot assume that the
application context can be obtained with
WebApplicationContextUtils.getRequiredApplicationContext(aServletContext).
Luckily, it is easy to write my own
What is the use case where the context can not be found via
WebApplicationContextUtils.getRequiredApplicationContext(aServletContext).?
Juergen
On 9/3/06, Erik Brakkee [EMAIL PROTECTED] wrote:
Hi,
I have done some work to locate the Spring application context in
another way. Both
Juergen Donnerstag wrote:
What is the use case where the context can not be found via
WebApplicationContextUtils.getRequiredApplicationContext(aServletContext).?
The use case is where existing code is used which has its own method of
accessing Spring configuration such as using
fair enough, its in svn-IgorOn 9/3/06, Erik Brakkee [EMAIL PROTECTED] wrote:
Hi,I have done some work to locate the Spring application context inanother way. Both wicket-spring and wicket-spring-annot assume that theapplication context can be obtained
