Invoke the operation with the specified name and returns a result set consisting of configuration propeties.
Plugin developers must write implementations of this method with the awareness that operations are cancelable and should prepare for such a possiblity in the code. For example, a user may request that an operation be canceled, or an operation may be taking to long and it should be canceled due to a timeout expiration. When an operation invocation is canceled, the thread that is invoking this method will be {@link Thread#interrupt() interrupted}. The plugin writer has a choice to make - either write this method implementation such that it ignores cancelation requests (in effect continue doing what it is doing and return normally) or handle the cancelation request and stop doing what it is doing and throw an {@link InterruptedException} to indicate the operation was aborted. Note that if an implementation does not throwan {@link InterruptedException}, the plugin container will assume the operation did not cancel itself. If, even after an interrupt, the implementation returns normally, the plugin container will assume the operation was successful and will be marked as such.
Plugin writers are encouraged to check the current thread's {@link Thread#isInterrupted()} method periodicallyto catch cancellation requests, as well as catching and processing {@link InterruptedException} appropriately.Plugin writers must also ensure that they do not leave the managed resource in an inconsistent state after being canceled or timed out.
If a plugin determines that the operation invocation failed for whatever reason, this method must throw an Exception, which indicates a failure. If this method returns normally with any {@link OperationResult} (even if it is null), the operation invocation will assumedto have been a success. The only caveat is if the returned object has its {@link OperationResult#setErrorMessage(String) error message} set, in which case, the operation is alsoassumed to have failed.
From RHQ4.9 on, plugin developers should check {@link org.rhq.core.pluginapi.component.ComponentInvocationContext#isInterrupted()}instead of {@link Thread#isInterrupted()}. An instance of this class is created by the plugin container and can be returned by calling {@link org.rhq.core.pluginapi.inventory.ResourceContext#getComponentInvocationContext()}.
@param name the name of the operation
@param parameters the parameters passed to the operation; even for operations with no parameters, an emptyconfig will be passed in by the plugin container
@return the result of the invocation
@throws InterruptedException if this operation was canceled
@throws Exception if failed to invoke the operation on the resource