A best practices guide for security in Seam seems to be in order. I think the use cases can be boiled down to a few scenarios, then an explanation as to how to address them will tell you whether the present mechanisms are sufficient, or if an Acegi mechanism is needed.
I am a big believer in addressing security via AOP because I don't really believe that you can know exactly how you want to address security at POJO compile-time (and over the life of a project, security requirements can change drastically). But if you can take a project and then apply AOP rules before deployment, this is a very flexible solution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954868#3954868 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954868 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
