MainDeployer was orginally slated to be an instance of DeployerMBean,
but someone refactored that interface such that it would not apply here
anymore...
--jason
David Jencks wrote:
>After enthusiastically using mbean proxies for a while now I'm going to
>turn around and agree with Andreas that they are kind of a bad idea. For
>instance, I think they led Jason to not put the MainDeployer as an
>attribute of the scanner because Main Deployer and the farm deployer don't
>extend a common interface. All they need is to have some of the same
>methods.
>
>btw notice I am saying farm deployer should be like MainDeployer, and not
>extend DeployerMBean.
>
>david jencks
>
>On 2002.03.06 01:47:45 -0500 Jason Dillon wrote:
>
>>>
>>>So you want to have an interface floating around even it is only used
>>>
>>for
>>
>>>this MBeanProxy ?
>>>
>>In short yes. I would rather have calls like
>>
>>serviceController.create(objectName);
>>
>>over
>>
>>server.invoke(controllerName,
>> new Object[] { objectName },
>> new String[] { ObjectName.class.getName() });
>>
>>It is easier to read/maintain, provides some level of type safety...
>>simplifies the client code.
>>
>>--jason
>>
>>
>>_______________________________________________
>>Jboss-development mailing list
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/jboss-development
>>
>>
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development