BUG-7608: use blueprint action-provider/action-service 15/51115/2
authorRobert Varga <rovarga@cisco.com>
Fri, 27 Jan 2017 12:47:21 +0000 (13:47 +0100)
committerRobert Varga <nite@hq.sk>
Mon, 30 Jan 2017 15:06:11 +0000 (15:06 +0000)
commit0d5442f3684c32b084a95ee38589c6fee576554f
tree794061624ed208805e20c3faa1d8b251887849e7
parenta2c0d5a3f660e899967a39767f3c227eb4bcc826
BUG-7608: use blueprint action-provider/action-service

The contract for RPC services containing Routed RPCs (RFC7950
actions) with respect to routing is different from normal RPCs.

In order to properly express dependencies, it needs a concept
of a promise to register instantiations (action-provider)
and the dependency on that promise (action-service). Use these
concepts instead of realying on rpc-service which happens to
work due to sal-remoterpc-connector (incorrecty) providing
the equivalent of action-provider for all Routed RPCs defined
in the local SchemaContext.

Change-Id: Iaad5b5b0b4384a2e7d6302bd7de5bfa00c24d89b
Signed-off-by: Robert Varga <rovarga@cisco.com>
applications/lldp-speaker/src/main/resources/org/opendaylight/blueprint/lldp-speaker.xml
openflowplugin-impl/src/main/resources/org/opendaylight/blueprint/openflowplugin-impl.xml