Hi All,
Most of Us will be very keen about Debugging the Code via Logging , this is Because this Prints the line it need .
So here is a solution for you and how to implement in Endeca. By Default Endeca OOTB code has very limited set of Logging . If you want to enable logging , most of the Class does not extend the Generic Service so no logging !! Dont Worry, Blindly Follow the Below Steps , you can enable logging for your Application .
I would Recommend of using the Same logging all the Places , because when you enable in one Component all the Corresponding components will print it from Starting of the Request and When Request is Becoming Death.
you can use the below snippet wherever it is required .
VariableArgumentApplicationLogging mLogger = AssemblerTools.getApplicationLogging();
usauge will be as follows mLogger.isLoggingDebug()
apart from this you will get all the loggings .
Happy Logging !!!!
Most of Us will be very keen about Debugging the Code via Logging , this is Because this Prints the line it need .
So here is a solution for you and how to implement in Endeca. By Default Endeca OOTB code has very limited set of Logging . If you want to enable logging , most of the Class does not extend the Generic Service so no logging !! Dont Worry, Blindly Follow the Below Steps , you can enable logging for your Application .
I would Recommend of using the Same logging all the Places , because when you enable in one Component all the Corresponding components will print it from Starting of the Request and When Request is Becoming Death.
you can use the below snippet wherever it is required .
VariableArgumentApplicationLogging mLogger = AssemblerTools.getApplicationLogging();
usauge will be as follows mLogger.isLoggingDebug()
apart from this you will get all the loggings .
Happy Logging !!!!
No comments:
Write comments