On Mon, 29 Jul 2002 [EMAIL PROTECTED] wrote:
> Date: Mon, 29 Jul 2002 11:10:14 -0700 (PDT)
> From: [EMAIL PROTECTED]
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: List Tomcat-Dev <[EMAIL PROTECTED]>
> Subject: catalina.mbeans package
>
> I'm a bit confused of what's in catalina.mbeans.
>
> My understanding of model mbeans is that we use the modeler
> and the xml description - what's the role of all the
> classes like LoggerMBean, etc ?
>
Most of the time, you want MBeans to directly delegate attribute read and
write operations to the corresponding component object. Sometimes,
though, that is not possible (for example, when the component getter takes
an actual object, and the MBean takes a string containing the MBean name).
Thus, you can subclass the provided base ModelMBean class and override
just the methods you care about -- everything else will pass through with
no changes.
> There is also some logic that goes inside the Mbean wrapper
> that is very strange - for example ConnectorMBean.getClientAuth().
> The logic should be in the object itself ( i.e. add get/setClientAuth
> to CoyoteConnector ), not in the JMX wrappers.
>
> Can anyone clarify this a bit ?
There are a bunch of methods on the Connector implementations that are not
exposed in Connector.java itself -- and we didn't want to change Connector
due to backwards compatibility concerns. Therefore, there's some special
case stuff on the various implementations.
In 5.0, this is definitely something that should be refactored in the
Connector interfaces so it doesn't have to be special cased.
>
> Costin
>
Craig
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
