Workaround for Node.fromString 19/15519/1
authorSam Hague <shague@redhat.com>
Fri, 20 Feb 2015 01:43:11 +0000 (20:43 -0500)
committerSam Hague <shague@redhat.com>
Fri, 20 Feb 2015 01:43:11 +0000 (20:43 -0500)
commit1e775d6f9b5702eb76216798d7909fa1c9555deb
tree0f4964ec67496eb4819eb97e92f91011d6dbaaa7
parent333bb9c494b25538d842bc0931cc0d776f000256
Workaround for Node.fromString

Added getnode(id) API to plugin ConnectionService interface to get the node requested by the id.

Also found some cases in the northbound that were using the fromString so replaced them with getNode.

Change-Id: I47dd6bb6cb432d6309744dd0206412a8a6037281
Signed-off-by: Sam Hague <shague@redhat.com>
integrationtest/src/test/java/org/opendaylight/ovsdb/integrationtest/plugin/OvsdbPluginIT.java
integrationtest/src/test/java/org/opendaylight/ovsdb/integrationtest/plugin/OvsdbPluginV3IT.java
northbound/src/main/java/org/opendaylight/ovsdb/northbound/OvsdbNorthboundV2.java
plugin-shell/src/main/java/org/opendaylight/ovsdb/plugin/shell/PrintCache.java
plugin-shell/src/test/java/org/opendaylight/ovsdb/plugin/shell/PrintCacheTest.java
plugin/src/main/java/org/opendaylight/ovsdb/plugin/api/OvsdbConnectionService.java
plugin/src/main/java/org/opendaylight/ovsdb/plugin/impl/ConnectionServiceImpl.java