Fix Match intersection logic 87/987/1
authorAlessandro Boch <aboch@cisco.com>
Sat, 24 Aug 2013 02:43:32 +0000 (19:43 -0700)
committerAlessandro Boch <aboch@cisco.com>
Sat, 24 Aug 2013 02:43:58 +0000 (19:43 -0700)
commitf69f22a30c6e21cd61b7221de4ab5fd4a69a655f
tree54e4204d667cec8f0d2d8b0e5f1dbaa1fc62711f
parent96d2f3b1bc12f6db46bece17ef2982d4b7c73f80
Fix Match intersection logic

    - Change in Match.java: Empty match represents all packets (universal set) while empty set is the null match.
                        So, in case of no intersection, return a null Match.
                            intersect() and getIntersection() optimized in case of universal and empty sets
    - Changes in MatchTest.java to junit the above changes
    - Change in FlowEntry.java: Match.mergewithFilter() is now returning a new Match instance

Change-Id: Idd3ff80d2fbcc11c3f83757268806596b7b2fc50
Signed-off-by: Alessandro Boch <aboch@cisco.com>
opendaylight/forwardingrulesmanager/api/src/main/java/org/opendaylight/controller/forwardingrulesmanager/FlowEntry.java
opendaylight/sal/api/src/main/java/org/opendaylight/controller/sal/match/Match.java
opendaylight/sal/api/src/test/java/org/opendaylight/controller/sal/match/MatchTest.java