This is an automated email from the ASF dual-hosted git repository. garydgregory pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/commons-xml.git
commit 258a634df6dce9ff9c9896b1cc028f239a24d7b7 Author: Gary Gregory <[email protected]> AuthorDate: Fri Aug 28 14:33:24 2026 -0400 Javadoc: "hardening" -> "secure/securing" wording to match new class and method names. Rename test methods. --- src/test/java/org/apache/commons/xml/ResetSecureTest.java | 4 ++-- src/test/java/org/apache/commons/xml/SaxonXPathExternalCallsTest.java | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/test/java/org/apache/commons/xml/ResetSecureTest.java b/src/test/java/org/apache/commons/xml/ResetSecureTest.java index 4264c08..a0ce73e 100644 --- a/src/test/java/org/apache/commons/xml/ResetSecureTest.java +++ b/src/test/java/org/apache/commons/xml/ResetSecureTest.java @@ -37,12 +37,12 @@ import org.xml.sax.XMLReader; /** - * Checks that the JAXP {@code reset()} lifecycle methods do not strip the hardening floors. + * Checks that the JAXP {@code reset()} lifecycle methods do not strip the secure floors. * * <p>The JAXP reset contract returns an object to its just-created state, and the stock JDK / Xerces implementations take that literally: they re-install * their initial (null) resolvers, silently removing any floor the secure wrappers installed after creation. Each test resets a secure object and asserts * that an external reference is still either blocked at parse or resolved to empty content afterwards; the tests are skipped on platforms whose - * implementation does not support {@code reset()} at all (there the hardening cannot be stripped in the first place).</p> + * implementation does not support {@code reset()} at all (there the securing cannot be stripped in the first place).</p> */ class ResetSecureTest { diff --git a/src/test/java/org/apache/commons/xml/SaxonXPathExternalCallsTest.java b/src/test/java/org/apache/commons/xml/SaxonXPathExternalCallsTest.java index 63c540f..08c2783 100644 --- a/src/test/java/org/apache/commons/xml/SaxonXPathExternalCallsTest.java +++ b/src/test/java/org/apache/commons/xml/SaxonXPathExternalCallsTest.java @@ -34,7 +34,7 @@ * * <p>Saxon ships several XPath 3.1 functions that open arbitrary URIs during evaluation. None require a context node; each is triggered purely by the string * URI it receives. They are <em>not</em> classified as extension functions in Saxon's vocabulary, so disabling {@code ALLOW_EXTERNAL_FUNCTIONS} is not enough - * to block them; a complete hardening has to close the URI-resolution path.</p> + * to block them; a complete secure has to close the URI-resolution path.</p> * * <p>Each fixture under {@code src/test/resources/leaked/} contains the {@link #MARKER} string. The tests dispatch the URI-fetching function at the file's URL * and check whether the marker reaches the result.</p> @@ -61,7 +61,7 @@ private static void assertCallExcludesMarker(final XPathFactory factory, final S try { result = evaluateAsString(factory, expression); } catch (final Exception e) { - return; // hardening blocked at evaluation; acceptable outcome. + return; // secure blocked at evaluation; acceptable outcome. } assertFalse(result.contains(MARKER), "Securing did not block the external reference; result contained marker '" + MARKER + "'.\nFull result:\n" + result);
