[jboss-dev-forums] [Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme
alesj
do-not-reply at jboss.com
Wed Sep 19 14:25:03 EDT 2007
OK, let me see if I get this ManagedOperation invocation. :-)
ManagementViewImpl loads profile == prepares Managed objects (props, operations). This means preparing proxies to expose to client via Dispatcher.singleton.
Once the ManagedOperation is invoked on the client side, it goes through the ProfileService subsystem via Connector(MBean) over ProfileServiceInvocationHandler which checks if it's actually ManagedOperation invocation (oid starting with ProfileService.ManagedOperation@ as it was set in proxy wrapper), which then delegates to ManagementViewImpl.invoke().
What I'm missing is that ManagementViewImpl.createOperationProxies(Set ops) is missing actual runtime component ref (name of the bean/service in MC or the bean/service itself).
Or how/where did you intend to get it?
Via ManagementObjectID --> ManagedObject.name?
| ManagementObjectID id = (ManagementObjectID) annotations.get(ManagementObjectID.class.getName());
| if (id != null)
| {
| if (value == null || value.getMetaType().isSimple() == false)
| {
| log.warn("Cannot create String name from non-Simple property: "
| +property+", value="+value);
| continue;
| }
| SimpleValue svalue = (SimpleValue) value;
| String name = "" + svalue.getValue();
| managedObject.setName(name);
| }
|
What we should be adding is aspect(s) for every bean/service that we intend to be managed?
So that we know what is the whole chain of events that the actual change triggers, e.g. changing the DS url should flush the pool of connections, create new ones, ...
Right?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086276#4086276
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086276
More information about the jboss-dev-forums
mailing list