On Fri, 11 Apr 2025 23:05:51 GMT, Joe Wang <jo...@openjdk.org> wrote:
> Streamline the extension function control in the XPath API by relying solely > on > [XPathFunctionResolver](https://docs.oracle.com/en/java/javase/24/docs/api/java.xml/javax/xml/xpath/XPathFunctionResolver.html), > which provides a secure and developer-defined mechanism. Remove the feature > FEATURE_SECURE_PROCESSING and jdk.xml.enableExtensionFunctions from the > decision path that are redundant with regard to XPath's Extension Functions. > > Note the comment in JAXPExtensionsProvider, starting at "JAXP 1.3 spec says > When ...", was not accurate. Refer to the spec: > https://docs.oracle.com/en/java/javase/24/docs/api/java.xml/javax/xml/XMLConstants.html#FEATURE_SECURE_PROCESSING, > FSP does not have specific requirement for the XPath functions. > > Tests: > Tier1 - 3 passed with regard to this change. There were unrelated/known > failures (e.g. bug8329757). > JCK passed except the previously reported issue (JCK-7322355). This pull request has now been integrated. Changeset: cf0db963 Author: Joe Wang <jo...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/cf0db96314863376254bacbff4eefd13e3527707 Stats: 464 lines in 9 files changed: 211 ins; 241 del; 12 mod 8354084: Streamline XPath API's extension function control Reviewed-by: rriggs, naoto ------------- PR: https://git.openjdk.org/jdk/pull/24605
