Ben,
I agree that these 2 methods could be directly inserted in the UserDetails
interface but its your decision that counts there (as the father of the
child ;) ).
In fact I introduced them there first, but while modifying
DaoAuthenticationProvider I realized that if people simply changed the
On Dec 29, 2004, at 8:53 PM, Ben Alex wrote:
One issue I'd appreciate some comments on is container adapter
deprecation. I know some people use the JBoss container adapter (as
they need to use EJB security as well), but I've not heard of any
usage of the Resin, Tomcat or Jetty adapters. It
On Thu, 30 Dec 2004 15:13:18 -0500, Matt Raible wrote
Finally, the status of the project is up for discussion. I met Rod a
few days back and we briefly discussed making Acegi Security a formal
Spring subproject. This, coupled with a 1.0.0+ version number, would
make some people and
+1 even though here at Rutgers we are happily using sub-1.x versions in
production :-)
Scott McCrory wrote:
On Thu, 30 Dec 2004 15:13:18 -0500, Matt Raible wrote
Finally, the status of the project is up for discussion. I met Rod a
few days back and we briefly discussed
Sergio Berna wrote:
Andy,
I agree that filtering the method response is a fascinating area. The only
problem I have always found on filtering a method response is that it
doesn't scale properly when performance is an issue. I'm particularly
thinking on Collections here, where the full collection
Matt Raible wrote:
Using container-managed authentication usually only requires a handful
of lines in web.xml and a few more in a server-specific deployment
descriptor. This makes me wonder if there's a simpler way to
configure Acegi (consolidating filters?). Or maybe defaults can be
set in
