org.opendaylight.mdsal.binding.javav2.spec.base

Interface Action<P extends TreeNode,D extends InstanceIdentifier<P>,I extends Input<I> & Instantiable<I>,O extends Output<O> & Instantiable<O>>

All Superinterfaces:

Operation

All Known Subinterfaces:

ListAction<P,K,I,O>, TestOperationServiceInCont2Action, TestOperationServiceInContAction, TestOperationServiceInListAction

Functional Interface:

This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.

@FunctionalInterface
public interface Action<P extends TreeNode,D extends InstanceIdentifier<P>,I extends Input<I> & Instantiable<I>,O extends Output<O> & Instantiable<O>>
extends Operation

The "action" statement is used to define an operation connected to a specific container or list data node. The "action" statement defines an action node in the schema tree. Under the action node, a schema node with the name "input" and a schema node with the name "output" are also defined. The nodes "input" and "output" are defined in the module’s namespace. The difference between an action and an rpc is that an action is tied to a node in the datastore, whereas an rpc is not. Action replaces concept of routed RPC and comes up with implicit InstanceIdentifier context, whereas routed RPC defines explicit leaf for this purpose.

Method Summary

Modifier and Type	Method and Description
void	invoke(I input, D ii, RpcCallback<O> callback)

Method Detail

invoke

void invoke(I input,
            D ii,
            RpcCallback<O> callback)

Parameters:

input - Action input schema node

ii - implicit InstanceIdentifier connected to action, according to https://tools.ietf.org/html/rfc7950

callback - on success/failure callback