Quickfix: Remove deprecated providers from Restconf Application
authorVaclav Demcak <vdemcak@cisco.com>
Fri, 6 Mar 2015 13:36:50 +0000 (14:36 +0100)
committerVaclav Demcak <vdemcak@cisco.com>
Mon, 9 Mar 2015 14:42:25 +0000 (15:42 +0100)
commitc5c75f48fcc88bbcbf04768dddeb505d477ca114
tree1d58efaac2c9d9764d069b38ff76155deb05369e
parent7cd8d02ed66a4d041f58e1a539d72dca6d603691
Quickfix: Remove deprecated providers from Restconf Application

Jersey 1.17 has problem with multiple Entity providers,
which consumes same content-type and produces different
Entity class. In wiring phase it does not report any problems,
but in runtime it may select incorrect one, which
will result in IllegalArgumentException, which is not
reported.

So in order to unblock most of functionality, legacy
providers are disabled.

This will fix data-store access, but without
subsequent patches RPCs are not usable.

Change-Id: I860e162232d887d13629504421076495a50a075b
Signed-off-by: Vaclav Demcak <vdemcak@cisco.com>
opendaylight/md-sal/sal-rest-connector/src/main/java/org/opendaylight/controller/sal/rest/impl/RestconfApplication.java
opendaylight/md-sal/sal-rest-connector/src/main/java/org/opendaylight/controller/sal/restconf/impl/ControllerContext.java
opendaylight/md-sal/sal-rest-connector/src/main/java/org/opendaylight/controller/sal/restconf/impl/RestconfImpl.java
opendaylight/md-sal/sal-rest-connector/src/test/java/org/opendaylight/controller/sal/restconf/impl/test/URITest.java