Skip to content
This repository
branch: master

Migrate to using named loggers

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.
latest commit 47b600635a
Jean Helou jeantil authored
..
Octocat-spinner-32 app Migrate to using named loggers February 20, 2014
Octocat-spinner-32 conf Migrate to using named loggers February 20, 2014
Octocat-spinner-32 project - Updated docs for maven and fixed a rendering problem in the passwor… January 26, 2014
Octocat-spinner-32 public - Changed the assets directory for SecureSocial to avoid conflicts wi… November 14, 2012
Octocat-spinner-32 README Removed old installation instructions for the demo apps. December 24, 2012
README
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.

Something went wrong with that request. Please try again.