Project

Profile

Help

Bug #2272

XdmNode.BaseUri throws exception when NodeInfo.getBaseURI() returns null

Added by Max Toro over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
.NET API
Sprint/Milestone:
Start date:
2014-12-22
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.6
Fix Committed on Branch:
9.6
Fixed in Maintenance Release:

Description

Same as #1191, but on .NET

History

#1 Updated by O'Neil Delpratt over 6 years ago

  • Status changed from New to In Progress
  • Assignee set to O'Neil Delpratt
  • Priority changed from Low to Normal

Thanks for reporting the bug you found looking at it now.

#2 Updated by O'Neil Delpratt over 6 years ago

Hi, do you have a code snippet that reproduces the problem please?

#3 Updated by Max Toro over 6 years ago

var processor = new Processor();
var docb = processor.NewDocumentBuilder();
var node = docb.Build(XmlReader.Create(new StringReader("<a/>")));

Console.WriteLine(node.BaseUri);

#4 Updated by O'Neil Delpratt over 6 years ago

  • Status changed from In Progress to Resolved

Thanks for sending the repo. I managed to reproduce it. A similar fix has been applied to the BaseUri property in the XdmNode class which will be available in the next release.

As a workaround if possible you could set the baseUri where you create the XmlReader:

XmlReader reader = XmlReader.Create(new StringReader("<a/>"), null, "http://example.com");

#5 Updated by O'Neil Delpratt over 6 years ago

  • Status changed from Resolved to In Progress

I am opening this again as the fix was not complete. I have created some nunit test cases to test for regression in future release.

#6 Updated by O'Neil Delpratt over 6 years ago

Bug fixed now in the Model.cs file. Fix committed to subversion.

#7 Updated by O'Neil Delpratt over 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

#8 Updated by O'Neil Delpratt over 6 years ago

  • Found in version changed from 9.6.0.3 to 9.6

#9 Updated by O'Neil Delpratt over 6 years ago

  • Fixed in version set to 9.6.0.4

Bug fix applied in the Saxon 9.6.0.4 maintenance release.

#10 Updated by O'Neil Delpratt over 6 years ago

  • Status changed from Resolved to Closed

#11 Updated by O'Neil Delpratt over 5 years ago

  • Sprint/Milestone set to 9.6.0.4
  • Applies to branch 9.6 added
  • Fix Committed on Branch 9.6 added
  • Fixed in Maintenance Release 9.6.0.4 added

#12 Updated by O'Neil Delpratt over 5 years ago

  • Sprint/Milestone changed from 9.6.0.4 to 9.6.0.3
  • Fixed in Maintenance Release 9.6.0.3 added
  • Fixed in Maintenance Release deleted (9.6.0.4)

#13 Updated by O'Neil Delpratt over 5 years ago

  • Sprint/Milestone changed from 9.6.0.3 to 9.6.0.4
  • Fixed in Maintenance Release 9.6.0.4 added
  • Fixed in Maintenance Release deleted (9.6.0.3)

Please register to edit this issue

Also available in: Atom PDF