Sorry. I'm not familiar with JMS. This notion of properties just looks like the MDC to me (and that's exactly how I would handle hostname if it wasn't natively supported). Is there some other difference? I don't know how these "properties" work exactly, but I don't want to have to set them at each logging call.
The MDC will work for me, I think. It's just sub-optimal to have applications set their hostname when they start up, cuz I still think hostname is fundamental enough to be supported. dan Ceki Gülcü <[EMAIL PROTECTED]> on 12/12/2002 04:51:53 PM Please respond to "Log4J Developers List" <[EMAIL PROTECTED]> To: "Log4J Developers List" <[EMAIL PROTECTED]> cc: Subject: RE: Hostname support in PatternLayout (patch included) I did not suggest that we use JMS but the properties as in JMS. Sorry, apparently I was not very clear. More concretely, we add a new field "properties" which is a hashtable that carries any number of key-value pairs. Hostname becomes just a particular key. Is that any clearer? At 15:50 12.12.2002 -0500, [EMAIL PROTECTED] wrote: >And JMS is a fine solution if you can use JMS. But if you aren't using >J2EE, you can't use JMS. Running tomcat/apache as an app server lends >itself to not knowing which host the message came from. Surely I'm not the >only one with a central repository of logs coming from various hosts who >can't use JMS? > >To me, hostname is simple and obvious. It's up there with thread name and >class name as fundamental information to be present in a log. Username, and >session id are J2EE-specific concepts. Or more generally, they are concepts >that different app writers might interpret differently, and so they >shouldn't be in some canonical list of things you can log. But hostname? >Hostname is canonical. Everyone knows what it means, and everyone with a >remote configuration needs to know it. Thus, I think log4j should support >hostname retrieval natively. > >dan -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions Health Services Corporation and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
