Re: [openflowplugin-dev] Can anybody propose a better solution for this https://bugs.opendaylight.org/show_bug.cgi?id=4281?
Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
the reason for removing yang files with rpcs inside is:
This bug emerged in dlux project as it is not possible there to distinguish between real service (exposed in md-sal) and API description (never exposed, polluting dlux UI).
Reverting that change will help testing but will damage dlux. I believe that solution should be based on more informations:
- @Tony: when will be the support for yang exclusion ready?
- @dlux-dev: can you guys live with having that bug reappeared till end of Beryllium?
From: openflowplugin-dev-bounces@... [openflowplugin-dev-bounces@...] on behalf of Yang, Yi Y [yi.y.yang@...]
Sent: Monday, September 21, 2015 14:02
To: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco); openflowplugin-dev@...
Cc: dev@...; openflowjava-dev@...
Subject: Re: [openflowplugin-dev] Can anybody propose a better solution for this https://bugs.opendaylight.org/show_bug.cgi?id=4281?
Thanks Tony, so can openflowjava guys help get it fixed in master tree?
From: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco) [mailto:ttkacik@...]
The fix is acceptable, since original pom file was messing with MD-SAL packaging, whichj may lead to incorrect behaviour if someone
used this models in their models.
On Behalf Of Yang, Yi Y
I encountered this bug https://bugs.opendaylight.org/show_bug.cgi?id=4281
Caused by: java.lang.IllegalStateException: Resource '/META-INF/yang/openflow-instruction.yang' is missing
The issue is fixed after I applied this patch https://git.opendaylight.org/gerrit/#/c/27172/, I'm not sure if it is acceptable, or do you have any better way to fix this?
I wonder why other openflowplugin unit tests didn’t encounter such issues although they also used AbstractDataBrokerTest.