Your welcome.

The fix was designed to be minimally intrusive into the existing codebase
while fixing the problem.  I'm not familiar with the design goals of the
log4j jmx package, so I tried to modify it as little as possible.   If
there is something I can do to make it better, please let me know. 

Thanks,
Bill

On Mon, 2 Jun 2003, Ceki [iso-8859-1] Gülcü wrote:

> Bill,
> 
> Thank you for reporting this bug and the associated fix. This is very helpful.
> 
> At 07:39 AM 5/28/2003 -0400, you wrote:
> 
> >The current JMX implementation in Log4J is in violation of the JMX
> >Specification versions 1.1 and 1.2.  These specifications require that
> >attribute names and parameter names on MBeans be valid Java identifiers.
> >
> >See Chapter 2 of the JMX 1.1 or 1.2 Specification.
> >
> >As a result, the JMX facade shipped with Log4J will not run on Sun's
> >JMX Reference Implementation version 1.2.  I have not tried version 1.1.
> >
> >The attached patch fixes this problem by mangling the attribute and
> >parameter names into legal Java identifiers.
> >
> >The patch also flags attributes that do not support writes as read-only.
> >
> >Thanks,
> >
> >Bill


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to