Le 26/02/2015 19:42, Raphaël Ouazana-Sustowski a écrit :
Hi,
Le 2015-02-26 12:57, Jephte Clain a écrit :
thanks for the tip. but the DEBUG log is not as complete as I expected...
now if I want to log a message, what should I use? is
java.lang.System.out.println() sufficient, or is there another
dedicated function?
println is generally sufficient for quick debugging. If you want
something more evolved, you can access slf4j api, for example:
var logger = org.slf4j.LoggerFactory.getLogger("scripting");
logger.warn("oups!");
thanks. I want to log messages on the same "level" than lsc itself, so
this is the way to go.
best regards,
--
Jephté CLAIN | Développeur / Intégrateur d'applications
Service Systèmes d'Information http://dsiun.univ-reunion.fr
Tel: +262 262 93 86 31 || Mobile: +262 692 29 58 24 ||
http://www.univ-reunion.fr
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
