Bug-6195: Fix issue with leafSetEntryNode in SchemaTracker
Changed SchemaTracker:leafSetEntryNode so that if LeafSetEntryNode
is present without it's parent LeafEntryNode in data-change notification,
it's serialization is handled properly. The existing leafSetEntryNode
functionality is kept around for API compatability reasons, but should
be removed in Boron as stated in the FIXME.
Change-Id: I6cf936752588c671268d11a0c277ccccd806e086
Signed-off-by: Ajay <ajayl.bro@gmail.com>
Signed-off-by: Ryan Goulding <ryandgoulding@gmail.com>