Bug #4664

Xerces bug: Wrong value of xml:base attribute after resolving XInclude references

Added by O'Neil Delpratt over 1 year ago. Updated over 1 year ago.

In Progress
Third-party product
Start date:
Due date:
% Done:


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


The following Xerces bug is affecting several users:

This bug causes the wrong value of xml:base attribute after resolving XInclude references. One user applies a the patch in a jar file that is included on the Java classpath when Saxon is invoked. It would be good to apply this patch internally with Saxon as part of the issued product.

This affects: Saxon-J, Saxon.NET and Saxon/C


#1 Updated by O'Neil Delpratt over 1 year ago

  • Status changed from New to In Progress
  • Applies to branch deleted (9.9)

bug fix applied to Saxon .NET. Leaving this bug issue open until fix is applied on Saxon-J and Saxon/C.

#2 Updated by Michael Kay over 1 year ago

  • Assignee set to Norm Tovey-Walsh

#3 Updated by Michael Kay over 1 year ago

Apart from fixing this bug, I think there are a number of other changes that could be useful in terms of improving the integration between Xerces and Saxon. For example, we could consider defining a "SAX3" interface that resolves some of the long-standing issues in namespace handling and that removes the current duplication whereby both Xerces and Saxon maintain full capability for resolving QNames, without directly sharing the means of doing so.

Several Saxon users (Oxygen and DeltaXML to my knowledge) are understood to ship their own Xerces variants, which suggests that it might be possible to establish a community to take such a project forward, either on the main Apache development branch for Xerces or as a community fork.

Please register to edit this issue

Also available in: Atom PDF