On Tue, May 23, 2017 at 8:12 AM, Robert Varga <n...@hq.sk> wrote: > On 23/05/17 16:50, Vishweshwar Hegde wrote: > > Thanks Robert for the information. > > > > Please refer below scenario: > > public static final QName QNAME = QName.create(XYZ.QNAME, > "abc").intern(); > > public static final YangInstanceIdentifier.NodeIdentifier NODEID = new > YangInstanceIdentifier.NodeIdentifier(QNAME); > > > > In our cohort flow for "abc" input value from NBI is "123" cohort > validation should change to "999". > > > > Any pointers for this scenario? > > At Tom already mentioned, validation is dealing with immutable data and > cannot change it, as that would render any model-defined validation > useless (i.e. what if the new value does not conform to the model?). >
fwiw, model-defined validation seems to happen after the commit cohort validation > > The API is limited strictly to implementing semantic checks which are > not expressible in YANG. > > Any transformation needs to happen elsewhere -- but details on where and > how depend very much on the use case and expectations of the complete > solution. > > Regards, > Robert > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
