Thanks! So it looks like at the INFO level, we should be logging all the interface calls for CentralAuthenticationService (and the params, return values).
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Mon, Feb 2, 2009 at 11:12 AM, Andrew Feller <[email protected]> wrote: > Scott, > > Most of our needs for INFO logging are currently being met in CAS3 with the > primary tasks of CAS: create TGT, destroy TGT, grant ST, validate ST, # of > tickets removed from registry. It would be nice to know when individual > service logout requests are being made to previously authenticated services. > As for DEBUG logging, I am satisfied as long as situation information > such as URLs, ticket IDs, service URLs are logged where necessary. > > Thanks, > A- > > > On 2/2/09 9:41 AM, "Scott Battaglia" <[email protected]> wrote: > > All, > > In order to ease maintenance and increase our internationalization, I'm > looking at using AspectJ to add logging to all of our classes (well with > some limitations, as I currently added TRACE logging to toString() ;-)). > > TRACE, ERROR, FATAL are obvious in what they should log. Since you guys > are the deployers, what would you like to see logged at the INFO and DEBUG > levels? > > Thanks > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > ------------------------------ > _______________________________________________ > cas-dev mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas-dev > > > -- > Andrew Feller, Analyst > LSU University Information Services > 200 Frey Computing Services Center > Baton Rouge, LA 70803 > Office: 225.578.3737 > Fax: 225.578.6400 > > _______________________________________________ > cas-dev mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas-dev > >
_______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
