Restrictions on extension functions has been removed in the XPath API, specifically those imposed by [FEATURE_SECURE_PROCESSING (FSP)](https://docs.oracle.com/en/java/javase/23/docs/api/java.xml/javax/xml/XMLConstants.html#FEATURE_SECURE_PROCESSING) and the `jdk.xml.enableExtensionFunctions` property. Previously, for extension functions to work, even with a user-defined [XPathFunctionResolver](https://docs.oracle.com/en/java/javase/24/docs/api/java.xml/javax/xml/xpath/XPathFunctionResolver.html), FSP had to be set to false and `jdk.xml.enableExtensionFunctions` true. For example, an XPath created via the following factory would fail with an XPathExpressionException when encountering an Extension Function:

            XPathFactory xpf = XPathFactory.newInstance();
            xpf.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);


With this change, extension functions now work solely based on the presence of a properly registered [XPathFunctionResolver](https://docs.oracle.com/en/java/javase/24/docs/api/java.xml/javax/xml/xpath/XPathFunctionResolver.html), making extension straightforward:

            XPathFactory xpf = XPathFactory.newInstance();
            xpf.setXPathFunctionResolver(new MyXPathFunctionResolver());

The default value of FSP has also been changed from false to true. Since extension functions are no longer governed by this setting, and the default XPath limits already conform to the secure configurations, this update has no effect on standard XPath behavior.