[NETCONF-481] The MonitoringSchema should have a default constructor Created: 31/Oct/17  Updated: 30/Nov/21  Resolved: 30/Nov/21

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: YunBo He Assignee: Ivan Martiniak
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Microsoft Word [NETCONF-481] Steps to reproduce.rtf    
Issue Links:
Duplicate
duplicates NETCONF-589 Get rid of JAXB in netconf-monitoring Resolved

 Description   

The MonitoringSchema should have a default constructor like the MonitoringSession, otherwise, it will fail while execute the following code in JaxBSerializer
JAXB_CONTEXT = JAXBContext.newInstance(NetconfState.class);

it will result in
java.lang.NoClassDefFoundError: Could not initialize class org.opendaylight.netconf.monitoring.xml.JaxBSerializer
at org.opendaylight.netconf.monitoring.Get.handle(Get.java:67)
at org.opendaylight.netconf.impl.osgi.NetconfOperationRouterImpl$NetconfOperationExecution.execute(NetconfOperationRouterImpl.java:182)
at org.opendaylight.netconf.notifications.impl.ops.Get.handle(Get.java:56)
at org.opendaylight.netconf.impl.osgi.NetconfOperationRouterImpl$NetconfOperationExecution.execute(NetconfOperationRouterImpl.java:182)
at org.opendaylight.netconf.impl.osgi.NetconfOperationRouterImpl.executeOperationWithHighestPriority(NetconfOperationRouterImpl.java:111)
at org.opendaylight.netconf.impl.osgi.NetconfOperationRouterImpl.onNetconfMessage(NetconfOperationRouterImpl.java:84)
at org.opendaylight.netconf.impl.NetconfServerSessionListener.processDocument(NetconfServerSessionListener.java:113)
at org.opendaylight.netconf.impl.NetconfServerSessionListener.onMessage(NetconfServerSessionListener.java:86)
at org.opendaylight.netconf.impl.NetconfServerSessionListener.onMessage(NetconfServerSessionListener.java:29)

 Comments   
Comment by Sowmiya Chidambaram [ 22/Dec/19 ]

hi HeYunBo, I have prepared a patch for this issue. Could you please provide me the exact steps to reproduce the same, so that I can confirm my fix and deliver it.

Generated at Wed Feb 07 20:15:08 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.