Project

Profile

Help

Bug #2202

ExternalObjectType for Java and .NET

Added by Michael Kay almost 5 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Saxon extensions
Sprint/Milestone:
Start date:
2014-10-29
Due date:
% Done:

100%

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

Description

We are currently preparing 9.6 for release on .NET but it is already out on Java.

The class ExternalObjectType on the Java platform represents the type of a Java external object, while DotNetExternalObjectType does the same on the .net platform. Unfortunately they do not share code where they should, and the .net version incorrectly treats external types as being atomic.

We're therefore introducing a new abstract class for the generic concept on both platforms (to be called ExternalObjectType) with subclasses JavaExternalObjectType for the Java platform and DotNetExternalObjectType for .net.

Because this change replaces a concrete Java-specific class with an abstract class of the same name, any applications that create instances of the class may need to change to instantiate the subclass instead.

History

#1 Updated by Michael Kay almost 5 years ago

  • Status changed from New to Resolved

#2 Updated by O'Neil Delpratt almost 5 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in version set to 9.6.0.2

Bug fix applied to the maintenance release Saxon 9.6.0.2

#3 Updated by O'Neil Delpratt almost 4 years ago

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

Please register to edit this issue

Also available in: Atom PDF