Feature #4468
closed
.NET API: mechanism to bind URI to class containing extension functions
100%
Description
As illustrated by bug #4463, it can be frustrating on .NET to get dynamic loading working for extension functions: there are too many ways of getting the security settings wrong.
It would therefore be a good idea to expose in the API the mechanism that already exists for binding a URI to a class containing such functions. For example
Processor.BindExtensions(string uri, System.Type type)
The implementation can use
DotNetExtensionLibrary dotNetLib = ((ProfessionalConfiguration) config).getExtensionBinder("clitype");
dotNetLib.declareDotNetType(uri, type);
After this, the stylesheet/query can use the specified URI to invoke methods defined on this class.
Updated by O'Neil Delpratt about 4 years ago
- Status changed from New to In Progress
- Applies to branch 9.9, trunk added
I have started working on adding this method to the .NET API. There seems to be some underlying problem with the mechanism therefore investigating it further.
Updated by O'Neil Delpratt over 3 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Fix Committed on Branch 10, trunk added
Bug fixed as suggested in comment #0 by adding the BindExtensions method to the Processor object. Also added the interfacing method bindExtensions on the Configuration as a stub. Implementation added on the ProfessionalConfiguration for Saxon-PEN and SAxon-EEN.
Available for the next release of Saxon .NET.
Updated by Debbie Lockett over 3 years ago
Documentation under extensibility/dotnetextensions updated (as suggested over email) to suggest use of Processor. BindExtensions as alternative to dynamic loading.
Updated by O'Neil Delpratt over 3 years ago
Bug fix applied in the Saxon 10.3 maintenance release
Updated by O'Neil Delpratt over 3 years ago
- Status changed from Resolved to Closed
- Fixed in Maintenance Release 10.3 added
Please register to edit this issue
.