Hi Jason

> >Two things:
> >1) I encounter the MBeanProxy (jmx/src/main/org/jboss/mx/util)
> >in AbstractDeploymentScanner. Because maybe we are going
> >towards XMBean (ModelMBeans) this will not work anymore
> >because there is not Interface with XMBeans. Shouldn't we
> >mark the MBeanProxy as deprecated ?
> >
>
> God, I hope not.  Just because *MBean interfaces are going away, does
> not mean we can't keep an iterface around for this.

So you want to have an interface floating around even it is only used for
this MBeanProxy ?

> MBeanProxy makes the code to call operations on an MBean much eaiser to
> code and understand... plus takes care of those damn JMX exceptions.

Be my guest and create a MBeanServer wrapper catching all the JMX Exceptions
but MBeanProxy makes it not easier because it ties an MBean to an class
and pervert the usage of JMX.

> >2) The AbstractDeploymentScanner is fixed linked with Main-
> >DeployerMBean and therefore I cannot use it for the Farm
> >anymore. Shouldn't it be an attribute which can be set from
> >outsite therefore another deployer than MainDeployer can
> >be used ?
> >We can still keep the MainDeployer as default.
> >
>
> This was the plan originally, execpt there is no common interface to use
> here.

We don't need a common interface. Just add an attribute taking the
ObjectName of the Deployer used to deploy.

Andy



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to