Comment out equality check in AbstractCompositeWriter.updateCurrent
authorMarek Gradzki <[email protected]>
Mon, 9 May 2016 08:13:24 +0000 (10:13 +0200)
committerMarek Gradzki <[email protected]>
Mon, 9 May 2016 10:44:43 +0000 (12:44 +0200)
commit50df3ef61f342f265222c289497c3143212d2c12
tree77cd48117dd159003127372727b53b8843af93d4
parentac5c0256f9b96deda69da1d250d55c5d00b83046
Comment out equality check in AbstractCompositeWriter.updateCurrent

There is a bug in ODL when checking auguments for equality:
https://git.opendaylight.org/gerrit/#/c/37719

Until the bug is fixed, updateCurrentAttributes will be invoked
even if there was no data change. It is customizer responsibility
to perform equality check if invoking update without actual data
change can cause side-effects in VPP.

Change-Id: Id72ec55ea7179330a4ebb1df49c29195908c5461
Signed-off-by: Marek Gradzki <[email protected]>
v3po/translate-impl/src/main/java/io/fd/honeycomb/v3po/translate/impl/write/AbstractCompositeWriter.java
v3po/v3po2vpp/src/main/java/io/fd/honeycomb/v3po/translate/v3po/vpp/BridgeDomainCustomizer.java
v3po/v3po2vpp/src/test/java/io/fd/honeycomb/v3po/translate/v3po/vpp/BridgeDomainCustomizerTest.java