1. Z.Archive.Openflowjava-Dev
  2. Messages

Re: [openflowplugin-dev] Li vs He - TransactionId and Error notifications

omar.m.dyson@gmail.com
 

Hi Michel,

You are right, this is what I'm expecting, but openflowplugin always report successful future even if the device return an Error

Here is a capture :

Thanks,






On 4 November 2015 at 14:30, Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...> wrote:

Hi Omar,

in Li-design you get a future object but the transactionId is null there.

Reason is simple: you do not need it. If there is an error message related to your flow then you will get failed future containing that error in exception.

If your future is successful then the flow has been accepted by device (flow-mod was sent followed by barrier request + reply).


See:

https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:He_vs_Li_comparison



Regards,

Michal




From: openflowplugin-dev-bounces@... <openflowplugin-dev-bounces@...> on behalf of omar dyson <omar.m.dyson@...>
Sent: Wednesday, November 4, 2015 15:34
To: openflowplugin-dev@...; openflowjava-dev
Subject: [openflowplugin-dev] Li vs He - TransactionId and Error notifications
 
Hi all,

In Helium RPC future result returned Transaction Id, example :

Future<RpcResult<AddFlowOutput>> rpcResult= salFlowService.addFlow(addFlowInput);
     if (rpcResult.get().isSuccessful()) {
          TransactionId id = rpcResult.get().getResult().getTransactionId()
     }

In Lithium code the getResult() always return null. Is that normal? How to get the transaction Id?

Also, the NodeErrorListener does not return OF errors as it is the case with Helium code.

I'm I missing something?

Regards,
Dyson
Join z.archive.openflowjava-dev@lists.opendaylight.org to automatically receive all group messages.