Quickfix: Remove deprecated providers from Restconf Application 28/16028/9
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)
commit32e32254cf269027359a786735f0b7fb580b39a4
tree763a102f5fbcd4718916d791fc1a1a7561e11f03
parentf55f03931ef55344b0fb71b75fb0cb577fa89d54
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