[BGPCEP-272] PCEP fix parser/serializer Created: 25/Aug/15  Updated: 03/Mar/19  Resolved: 25/Sep/15

Status: Resolved
Project: bgpcep
Component/s: PCEP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Claudio David Gasparini Assignee: Claudio David Gasparini
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 4181

 Description   

PCEP Activator parse PCEPEndPointsIpv6ObjectParser using PCEPEndPointsIpv4ObjectParser

regs.add(context.registerObjectParser(PCEPEndPointsIpv6ObjectParser.CLASS, PCEPEndPointsIpv6ObjectParser.TYPE,
new PCEPEndPointsIpv4ObjectParser()));
-------
Objects with 2 types as bandwidth, endpoints(Ipv4/Ipv6), ... are not serialized correctly.

Ex:

EndpointsObj.class is serialized with endpoints4Parser, whether its Ipv4 or Ipv6.

 Comments   
Comment by Claudio David Gasparini [ 28/Aug/15 ]

https://git.opendaylight.org/gerrit/#/c/26151/

Comment by Claudio David Gasparini [ 07/Sep/15 ]

Same issue detected for Path Key Object / sub object

final RROPathKey32SubobjectParser pathKeyParser = new RROPathKey32SubobjectParser();
regs.add(context.registerRROSubobjectParser(RROPathKey32SubobjectParser.TYPE, pathKeyParser));
regs.add(context.registerRROSubobjectParser(RROPathKey128SubobjectParser.TYPE, new RROPathKey128SubobjectParser()));
regs.add(context.registerRROSubobjectSerializer(
org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev131005.reported.route.object.rro.subobject.subobject.type.PathKeyCase.class,
pathKeyParser));

Comment by Claudio David Gasparini [ 16/Sep/15 ]

https://git.opendaylight.org/gerrit/#/c/26589/

Generated at Wed Feb 07 19:12:33 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.