Thanks for the clarification. Is there any way we can set the response code in the canCommit() method of the cohert in case of failure ?
Regards, -Satish From: Tom Pantelis [mailto:tompante...@gmail.com] Sent: Monday, April 03, 2017 7:34 PM To: Satish Dutt <sd...@advaoptical.com> Cc: tpant...@brocade.com; controller-dev@lists.opendaylight.org; controller-us...@lists.opendaylight.org Subject: Re: Getting RPC error when registering my cohert You need Boron SR3. The DOMDataTreeCommitCohortRegistry wasn't advertised prior to that. On Sun, Apr 2, 2017 at 8:01 AM, Satish Dutt <sd...@advaoptical.com<mailto:sd...@advaoptical.com>> wrote: Hi Thomas, I have taken the example code provided in the CarProvider for registering my cohert in my provider class. But whenever I am trying to register my cohert, I am always getting the ” RPC error DOMDataTreeCommitCohortRegistry not found “ . Below is my code snippet : @Override public synchronized Future<RpcResult<Void>> registerCommitCohort() { if (commitCohortReg.get() != null) { return RpcResultBuilder.<Void>success().buildFuture(); } final DOMDataTreeCommitCohortRegistry commitCohortRegistry = (DOMDataTreeCommitCohortRegistry) domDataBroker.getSupportedExtensions().get(DOMDataTreeCommitCohortRegistry.class); if (commitCohortRegistry == null) { // Shouldn't happen return RpcResultBuilder.<Void>failed().withError(ErrorType.APPLICATION, "DOMDataTreeCommitCohortRegistry not found").buildFuture(); } … … } I am using the mdsal-dom-api-2.1.0-Boron.jar . Is the issue related to the older jar version being used ? Regards -Satish
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
