Use a String Id for both Node and NodeConnector 84/3884/1
authorMoiz Raja <moraja@cisco.com>
Sat, 21 Dec 2013 01:53:14 +0000 (17:53 -0800)
committerMoiz Raja <moraja@cisco.com>
Sat, 21 Dec 2013 01:53:14 +0000 (17:53 -0800)
commit2f89a4e102ae31d29a42b44b11a7548a1feab1b7
tree1ff247409af68f37ab290df253f7f6d1a8fd55fb
parentb2b2cff46731661cffc4fcea32cc77f24ebe7366
Use a String Id for both Node and NodeConnector

Previously Node and NodeConnector were using NodeKey and NodeConnectorKey respectively as the Id. This causes problems
when you try to use some of the old north bound APIs as they expect to match a node or nodeconnector based on the string id
that is passed to it by the NB APIs

Change-Id: I697d8284f45c8b2d5f7dff327e045cf999d0c701
Signed-off-by: Moiz Raja <moraja@cisco.com>
opendaylight/md-sal/compatibility/sal-compatibility/src/main/java/org/opendaylight/controller/sal/compatibility/ComponentActivator.xtend
opendaylight/md-sal/compatibility/sal-compatibility/src/main/java/org/opendaylight/controller/sal/compatibility/MDSalNodeConnectorFactory.java [new file with mode: 0644]
opendaylight/md-sal/compatibility/sal-compatibility/src/main/java/org/opendaylight/controller/sal/compatibility/MDSalNodeFactory.java
opendaylight/md-sal/compatibility/sal-compatibility/src/main/java/org/opendaylight/controller/sal/compatibility/NodeMapping.xtend