fix JAXB usage/design bug in NeutronObject re. null tenant_id 26/75926/1
authorMichael Vorburger <vorburger@redhat.com>
Mon, 10 Sep 2018 14:18:11 +0000 (16:18 +0200)
committerMichael Vorburger <vorburger@redhat.com>
Mon, 10 Sep 2018 14:22:08 +0000 (16:22 +0200)
commit2508667ae1ec0d8aadd95585a8612471e0132b6c
treea63595effd4b7197b51985f8a845b4e75f39bd7f
parent9a88d4a81c10f2840fec44d9b2b4416d6440df44
fix JAXB usage/design bug in NeutronObject re. null tenant_id

@XmlElement on a (package visible..) field and then special logic in the
getter was perhaps an unholy combination.  I can't quite explain why it
worked most of the time but not always.  One would think that the tests
going through the getter should also execute that special logic, but
alas, clearly in some of the test runs (and perhaps in production...)
they did not, see the recurring NEUTRON-159 problem.

background: https://bugs.opendaylight.org/show_bug.cgi?id=4775 (and its
old https://git.opendaylight.org/gerrit/#/c/31324 and
https://git.opendaylight.org/gerrit/#/c/31361/)

JIRA: NEUTRON-159
Change-Id: I986dc6f4bea2f08becea21936bedd831643d212e
Signed-off-by: Michael Vorburger <vorburger@redhat.com>
neutron-spi/src/main/java/org/opendaylight/neutron/spi/NeutronObject.java