Correct - you follow the same basic registration as you did with VI3. The difference is you add that block that I specified above and attach it to the Extension. Once you do this, re-register your plugin and stop/start the VMware services (or reboot), it should display the correct strings.
Then, in your plugin code, you do something like this to setup the task (where YOUR_PACKAGE_NAME is the key you used to register, and YOUR_TASK_ID is the "com.netapp.yourcompany.yourTask" from above):
ExtensionManager extMgr = si.getExtensionManager();
Extension myExt = null;
try {
myExt = extMgr.findExtension(YOUR_PACKAGE_NAME);
}
catch (RemoteException e) {
// handle
}
ArrayList<ExtensionTaskTypeInfo> taskId = new ArrayList<ExtensionTaskTypeInfo>();
ExtensionTaskTypeInfo tmp = new ExtensionTaskTypeInfo();
tmp.setTaskID(YOUR_TASK_ID);
taskId.add(tmp);
myExt.setTaskList(taskId.toArray(new ExtensionTaskTypeInfo[http:// taskId.size() |http:// taskId.size() ])); // stupid auto formats should be <bracket> taskId.size() <bracket>
try {
extMgr.updateExtension(myExt);
}
catch (NotFound e) {
// handle
}
catch (RuntimeException e) {
// handle
}
catch (RemoteException e) {
// handle
}
I follow the basic registration as Example 3 in this doc: - the ONLY real difference is I add the ExtensionResourceInfo blocks for my tasks, attach that to the Extension and use the above method to setup the task.
