Hi,
I think the logging process is too complex (four levels, Information
Error Debug Warning), and few people use this complexity in jboss code.
I would propose only 2 levels:
- Information-Error always printed
- Debug-Warning printed only if debug flag is true, this flag would be a
parameter of ConsoleLogging (or Logger?), and could be toggled through
jmx (let's advertise localhost:8082 !)
We should also review the code to see what we really want to print.
Any comments?
Sebastien
Rickard �berg wrote:
>
> Hi!
>
> Justin Forder wrote:
> > Are there any documentation conventions for MLETs?
> >
> > A good UNIX configuration file would be largely composed of explanatory
> > text and commented-out examples.
>
> IMHO the current MLet conf style is seriously flawed. Not only is it a
> bad thing to have anonymous <ARG TYPE=.. VALUE=..> tags (which is
> which!?) but the JMX RI also does not support comments(!) in the file.
> Because of this I would generally recommend that MLets do not take any
> arguments, but instead are configure through get/set methods, whose
> values are set through the .jcml file (which do not have the above
> problems!).
>
> When I get the time I will convert as many MBeans as possible to support
> this style of configuration.
>
> regards,
> Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
