Bug 6163: fixed number of argument when resolving rpc input

[mdsal.git] / binding / yang-binding / src / main / java / org / opendaylight / yangtools / yang / binding / util / AbstractMappedRpcInvoker.java

diff --git a/binding/yang-binding/src/main/java/org/opendaylight/yangtools/yang/binding/util/AbstractMappedRpcInvoker.java b/binding/yang-binding/src/main/java/org/opendaylight/yangtools/yang/binding/util/AbstractMappedRpcInvoker.java
index 8ee514e53c16ff4ec1047e3090e3afb62d5d5915..b4839233276e51ec4ef5272c9ad68207b7c43884 100644 (file)
--- a/binding/yang-binding/src/main/java/org/opendaylight/yangtools/yang/binding/util/AbstractMappedRpcInvoker.java
+++ b/binding/yang-binding/src/main/java/org/opendaylight/yangtools/yang/binding/util/AbstractMappedRpcInvoker.java
@@ -45,7 +45,7 @@ abstract class AbstractMappedRpcInvoker<T> extends RpcServiceInvoker {
 
     @Override
     public final Future<RpcResult<?>> invokeRpc(@Nonnull final RpcService impl, @Nonnull final QName rpcName, @Nullable final DataObject input) {
-        Preconditions.checkNotNull(impl, "implemetation must be supplied");
+        Preconditions.checkNotNull(impl, "Implementation must be supplied");
 
         RpcMethodInvoker invoker = map.get(qnameToKey(rpcName));
         Preconditions.checkArgument(invoker != null, "Supplied RPC is not valid for implementation %s", impl);