struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norbert Harrer <nhar...@gmx.at>
Subject Re: Origin of struts log messages misleading
Date Tue, 21 Jul 2015 11:00:02 GMT
Alright. Only need to be patient then :-)

Thanks.

On 18.07.2015 19:55, Lukasz Lenart wrote:
> 2015-07-17 23:57 GMT+02:00 Norbert Harrer <nharrer@gmx.at>:
>> Hi.
>>
>> I noticed, that all log messages from struts look like this:
>>
>> Jul 17, 2015 11:31:39 PM com.opensymphony.xwork2.util.logging.jdk.JdkLogger
>> info
>> INFO: Parsing configuration file [struts-plugin.xml]
>> Jul 17, 2015 11:31:39 PM com.opensymphony.xwork2.util.logging.jdk.JdkLogger
>> info
>> INFO: Parsing configuration file [struts.xml]
>> Jul 17, 2015 11:31:39 PM com.opensymphony.xwork2.util.logging.jdk.JdkLogger
>> info
>> INFO: Choosing bean (struts) for (com.opensymphony.xwork2.ObjectFactory)
>>
>> They are all coming from the logging wrapper
>> com.opensymphony.xwork2.util.logging.jdk.JdkLogger.
>>
>> While this is true, wouldn't it be much more helpful if the log would show
>> the actual class that made the logger call?
>> Sometimes it's helpful to examine the source code of struts classes where
>> log messages come from. But that way it's very hard to find out where the
>> log message actually originated from.
> That's why we have deprecated the existing logging layer in XWork and
> switched to Log4j2 in Struts 2.5
>
>
> Regards


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Mime
View raw message