Using named loggers allows client applications to have a fine grained control over the library logs. An example could be logging all sent emails for tracking purpose without setting all the application's logs at DEBUG which can be extremely verbose. This commit names all the loggers used throughout securesocial, adds loggers to the sample app to demonstrate that there are no conflicts in defining a logger variable with the same name in the application code. Finally it changes the sample applications configuration to show how to set the log level for the securesocial loggers.
|app||Migrate to using named loggers|
|conf||Migrate to using named loggers|
|project||- Updated docs for maven and fixed a rendering problem in the passwor…|
|public||- Changed the assets directory for SecureSocial to avoid conflicts wi…|
|README||Removed old installation instructions for the demo apps.|
Sample SecureSocial 2 Application (Java version) ================================================= To run this sample you need to: 1) Create an application in the developer site of each provider you want to try and configure the OAuth settings in the securesocial.conf file. 2) Configure an email account that the app can use to send emails 3) Open the play console and execute the app Check the User Guide at http://securesocial.ws/guide/getting-started.html for more information on SecureSocial.