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 72e7345df3cb1082d1969b9c94787c69cefc7681
Author: Gary Gregory <[email protected]>
AuthorDate: Fri Aug 28 14:54:54 2026 -0400

    javadoc: Use "specification", not "spec".
---
 src/test/java/org/apache/commons/xml/AttackTestSupport.java | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/src/test/java/org/apache/commons/xml/AttackTestSupport.java 
b/src/test/java/org/apache/commons/xml/AttackTestSupport.java
index 1eb6e0f..b9b3574 100644
--- a/src/test/java/org/apache/commons/xml/AttackTestSupport.java
+++ b/src/test/java/org/apache/commons/xml/AttackTestSupport.java
@@ -114,14 +114,15 @@ public void setFeature(final String name, final boolean 
value) throws SAXNotReco
 
     /**
      * Strict reporter installed on every secure factory, parser, validator 
and transformer in the helpers below.
-     *
-     * <p>The secure layer signals every blocked external fetch and every 
SAX-fatal it could not silently skip via the standard JAXP error channels:
+     * <p>
+     * The secure layer signals every blocked external fetch and every 
SAX-fatal it could not silently skip via the standard JAXP error channels:
      * {@link ErrorListener#error(TransformerException)} / {@link 
ErrorListener#fatalError(TransformerException) fatalError} on the TrAX side and
      * {@link ErrorHandler#error(SAXParseException) error} / {@link 
ErrorHandler#fatalError(SAXParseException) fatalError} on the SAX side. Both 
Apache Xalan's
      * {@code DefaultErrorHandler(false)} and Saxon's {@code 
StandardErrorListener} are pathologically lenient defaults that swallow these 
events; SAX's
      * {@link DefaultHandler} treats {@code error} as a no-op. The test 
fixture replaces those defaults with a strict reporter that re-throws on every 
reported
-     * error or fatalError so the helpers can observe the block via the same 
mechanism the spec uses to surface it. Warnings stay silent: they are not 
security
-     * signals.</p>
+     * error or fatalError so the helpers can observe the block via the same 
mechanism the specification uses to surface it. Warnings stay silent: they are 
not
+     * security signals.
+     * </p>
      */
     static final class StrictReporter implements ErrorListener, ErrorHandler {
 

Reply via email to