> Must the SecurityManager follow certain rules (implement some interface > I don't know of) or can I write it "freehand"?
No and it's the main advantage of Spring compared to EJB's : it's non-invasive, which means there is no trace of Spring constraint in your code. The only "constraint" is that it has to be a POJO (Plain Old Java Object) and respect the JavaBean convention : private fields, and getter and setter for each field. The rest is just a matter of configuration in applicationContext.xml. Take a look at applicationContext.xml in CHS sample, and don't forget to look for the lines around some "OpenSessionInViewFilter" in web.xml. This is very important to understand. I'll add an example of my Security manager and the corresponding Spring configuration to the wiki page. But in fact as I can't introduce my SecurityManager without the surrounding classes, I'll make a more complete tutorial about that. I'll keep you notified. -- Sebastien ARBOGAST --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
