>> If JkLogLevel <= REQUEST ?
>
>Please, no more levels... Debug, info, error, etc is enough -
>request is
>not a level but a channel/log/whatever.
>What next, add a 'headers' level to display the headers ? Is
>headers<request ?
Good idea the dump of header, I'll often have to track problems
with them, seriously
>Add a worker.ajp13.logRequest property if you want, and use INFO level.
You're right it's better :
worker.ajp13.logRequest={The Proposed JkRequestLogFormat}
ie
worker.ajp13.logRequest="%b %w"
>> Why not use instead JkLogLevel INFO + REQUEST to explicitly
>> explain we want request logged
>
>Let's keep log level and option to the standard levels.
>
>I'm -1 on messing with the levels, almost everyone agrees on the
>4-5 levels ( see log4j, commons-loging, etc ) and separate 'channels'
>for logging different kinds of information.
Ok, let drop this.
>> >Here is an example:
>> >
>> >JkMount /*/servlet/ ajp13
>>
>> Great
>
>Not very great, the mapper is already very messy - and this
>shortcut will
>be hard to support in future, we have enough troubles with the
>standard
>mappoings.
>
>If you really need it, I'm ok if you check it in so you solve your
>problem, but I would leave it undocumented ( or documented as
>an experimental
>feature that might/will go away in future )
>
>A better solution ( IMHO ) would be for AutoAlias to automatically add
>a mapping for servlets and jsps, and maybe read a
>ctx_root/WEB-INF/jkmap.properties with additional mappings for the
>context.
You're speaking of jk 2.0 when Glenn works on jk 1.2.
Let say that these features (JkMount/JkAlias) will be present in jk 1.2 only
and will be replaced in jk 2.0
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
