After reading the code for DispatcherServlet, it said that the DispatcherServlet will create its own context based on the servlet's associated file and that the servlet's context will be parented by the global context configured via the ContextLoadListener. Each servlet's context is private to itself but, obviously, the global context is shared by all servlets.
Monday, February 22, 2010
02-19-2010
Started looking at Spring Security 3.0. Seems simple enough but I can't get it work along side Spring 3.0 MVC. The security servlet filter doesn't seem to think that an application context has been loaded. Ok, the solution is to bootstrap Spring via ContextLoaderListener like so:
org.springframework.web.context.ContextLoaderListener
After reading the code for DispatcherServlet, it said that the DispatcherServlet will create its own context based on the servlet's associated file and that the servlet's context will be parented by the global context configured via the ContextLoadListener. Each servlet's context is private to itself but, obviously, the global context is shared by all servlets.
After reading the code for DispatcherServlet, it said that the DispatcherServlet will create its own context based on the servlet's associated file and that the servlet's context will be parented by the global context configured via the ContextLoadListener. Each servlet's context is private to itself but, obviously, the global context is shared by all servlets.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment