Doesn't matter, YOU CAN keep those files separate, just give the following in:
prefix can be say your project name for example and spring's the folder or package where your xml config resources might be ... that way all your bean definitions would be available, I think it is a good practice to keep security config separate ... just a thought.
Addendum: This is in web.xml
Joined: Apr 23, 2009
thanks i will sure check on this
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Spring security: No bean named 'springSecurityFilterChain' is defined