Origin of struts log messages misleading

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: Parsin

Re: Origin of struts log messages misleading

Thanks, Martin, for your reply. But aren't you talking about my own logging messages? I was talking about the log messages from struts itself. Kindest Regards, Norbert. On 18.07.2015 02:16, Martin Gainty wrote: Norbert: you can always dig out the class name e.g. logger.getClass().getName()

Re: Origin of struts log messages misleading

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 : 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

Re: Origin of struts log messages misleading

tient then :-) Thanks. On 18.07.2015 19:55, Lukasz Lenart wrote: 2015-07-17 23:57 GMT+02:00 Norbert Harrer : 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-

Setting interceptor param on package level

Hi. A question just out of curiosity. Is it possible to set an interceptor parameter on the package level. For example I have a couple interceptor stacks more or less like this: true ERROR I want the Parameters for the ExceptionMappingIntercept