I've successfully used two different methods for getting the ApplicationContext which does not require the weird wiring of beans for the WicketServlet and requires no special Application classes.
1. See http://forum.springframework.org/viewtopic.php?t=3224 Scroll to the bottom. He extends ContextLoaderListener and provides a static reference to the AppContext. 2. Use SingletonBeanFactoryLocator or ContextSingletonBeanFactoryLocator. The API docs for SingletonBeanFactoryLocator explain exactly how to do it. Because I currently still have code using Spring MVC, I decided to use #1, so my old code can still access the AppContext as well as my new Wicket code. The second method will load up a second instance of the AppContext if you are already loading up one anywhere in the app. Anyone have any thoughts on these two methods? I think the advantages are that you can setup Wicket without any fancy jazz in the appContext. --Andrew ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
