1. There is a new feature which can help you writing the code when registering XMap mapped extensions

You need for this to extend DefaultComponent and instead of overwriting
registerExtension(..)
and unregisterExtension(..)
you should use
registerContribution(..)
and unregisterContribution(..)

These new methods are giving you each xmapped object, the target extension point and contributor component as arguments
So you don't need anymore to write code like:

 public void registerExtension(Extension extension) throws Exception {
       Object[] descriptors = extension.getContributions();
       if (descriptors.length == 0) return;
ComponentName name = extension.getComponent().getName(); for (Object desc : descriptors) {
           ListenerDescriptor lDesc = (ListenerDescriptor)desc;
           // do something with lDesc
        }
   }

but instead you can write it this way:

public void registerContribution(Object contribution, String extensionPoint, ComponentInstance contributor) {
           ListenerDescriptor lDesc = (ListenerDescriptor)desc;
// do something with lDesc }

You can still use the old method if you want.

2. I started working on an eclipse plugin to introspect NXRuntime components, extension points and extensions that are deployed in a running ECM application (or any NXRuntime instance) The ECM application may be located on remopte mahcines (remote connections are made through jboss-remoting)

The plugin is usable but still experimental. I will let you know when it will be fully functional.

Bogdan

_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm

Reply via email to