X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=opendaylight%2Fmd-sal%2Fsal-binding-api%2Fsrc%2Fmain%2Fjava%2Forg%2Fopendaylight%2Fcontroller%2Fsal%2Fbinding%2Fapi%2FRpcConsumerRegistry.java;h=0c5e7649f865403eb2a3c9903ff30223767d6f38;hb=919145b1bf7d68e436efa9b22c174965005a174a;hp=f71d69b860d5127ee0f01be5c409a319e36cfd6e;hpb=9070e358923aca6229137d46f9cae7ff458204dd;p=controller.git diff --git a/opendaylight/md-sal/sal-binding-api/src/main/java/org/opendaylight/controller/sal/binding/api/RpcConsumerRegistry.java b/opendaylight/md-sal/sal-binding-api/src/main/java/org/opendaylight/controller/sal/binding/api/RpcConsumerRegistry.java index f71d69b860..0c5e7649f8 100644 --- a/opendaylight/md-sal/sal-binding-api/src/main/java/org/opendaylight/controller/sal/binding/api/RpcConsumerRegistry.java +++ b/opendaylight/md-sal/sal-binding-api/src/main/java/org/opendaylight/controller/sal/binding/api/RpcConsumerRegistry.java @@ -7,19 +7,64 @@ */ package org.opendaylight.controller.sal.binding.api; +import org.opendaylight.controller.md.sal.binding.api.BindingService; import org.opendaylight.yangtools.yang.binding.RpcService; /** - * Base interface defining contract for retrieving MD-SAL - * version of RpcServices - * + * Provides access to registered Remote Procedure Call (RPC) service implementations. The RPCs are + * defined in YANG models. + *

+ * RPC implementations are registered using the {@link RpcProviderRegistry}. + * */ -public interface RpcConsumerRegistry extends BindingAwareService { +public interface RpcConsumerRegistry extends BindingAwareService, BindingService { /** - * Returns a session specific instance (implementation) of requested - * YANG module implementation / service provided by consumer. - * - * @return Session specific implementation of service + * Returns an implementation of a requested RPC service. + * + *

+ * The returned instance is not an actual implementation of the RPC service + * interface, but a proxy implementation of the interface that forwards to + * an actual implementation, if any. + *

+ * + * The following describes the behavior of the proxy when invoking RPC methods: + *

+ * + * The returned proxy is automatically updated with the most recent + * registered implementation. + *

+ * The generated RPC method APIs require implementors to return a {@link java.util.concurrent.Future Future} + * instance that wraps the {@link org.opendaylight.yangtools.yang.common.RpcResult RpcResult}. Since + * RPC methods may be implemented asynchronously, callers should avoid blocking on the + * {@link java.util.concurrent.Future Future} result. Instead, it is recommended to use + * {@link com.google.common.util.concurrent.JdkFutureAdapters#listenInPoolThread(java.util.concurrent.Future)} + * or {@link com.google.common.util.concurrent.JdkFutureAdapters#listenInPoolThread(java.util.concurrent.Future, java.util.concurrent.Executor)} + * to listen for Rpc Result. This will asynchronously listen for future result in executor and + * will not block current thread. + * + *

+     *   final Future> future = someRpcService.someRpc( ... );
+     *   Futures.addCallback(JdkFutureAdapters.listenInThreadPool(future), new FutureCallback>() {
+     *
+     *       public void onSuccess(RpcResult result) {
+     *          // process result ...
+     *       }
+     *
+     *       public void onFailure(Throwable t) {
+     *          // RPC failed
+     *       }
+     *   );
+     * 
+ * @param serviceInterface the interface of the RPC Service. Typically this is an interface generated + * from a YANG model. + * @return the proxy for the requested RPC service. This method never returns null. */ - T getRpcService(Class module); + T getRpcService(Class serviceInterface); }