This is an automated email from the ASF dual-hosted git repository. robertlazarski pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
commit 5ec4d1525eb830102168866727f7f5a5aebfb2ac Author: Robert Lazarski <[email protected]> AuthorDate: Wed Aug 5 14:47:30 2026 -1000 Drop third-party references from test documentation These comments explained themselves by pointing at who had said what, which is not information the code needs and not appropriate to carry in the tree. Same rationale stated without it. Co-Authored-By: Claude Fable 5 <[email protected]> --- .../addressing/AddressingResponseEndpointPolicyHandlerTest.java | 8 ++++---- .../org/apache/axis2/builder/MultipartFormDataBuilderTest.java | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/modules/addressing/test/org/apache/axis2/handlers/addressing/AddressingResponseEndpointPolicyHandlerTest.java b/modules/addressing/test/org/apache/axis2/handlers/addressing/AddressingResponseEndpointPolicyHandlerTest.java index 02ceaa84e2..6ddd9f110f 100644 --- a/modules/addressing/test/org/apache/axis2/handlers/addressing/AddressingResponseEndpointPolicyHandlerTest.java +++ b/modules/addressing/test/org/apache/axis2/handlers/addressing/AddressingResponseEndpointPolicyHandlerTest.java @@ -36,10 +36,10 @@ import org.apache.axis2.description.Parameter; * End-to-end coverage of the response-endpoint policy through the handler that * actually parses inbound WS-Addressing headers. * - * <p>This exists because neither the unit tests for the policy itself nor the - * reporter's proof-of-concept exercise the path an attacker actually has. The - * PoC builds a MessageContext and calls {@code setReplyTo} in Java before - * driving the transport sender, which no remote caller can do; the only way in + * <p>This exists because the unit tests for the policy call the check directly, + * which does not exercise the path an attacker actually has. Building a + * MessageContext and calling {@code setReplyTo} in Java before driving the + * transport sender is not something a remote caller can do; the only way in * from outside is a {@code wsa:ReplyTo} header on an inbound message, which is * what these tests send. */ diff --git a/modules/kernel/test/org/apache/axis2/builder/MultipartFormDataBuilderTest.java b/modules/kernel/test/org/apache/axis2/builder/MultipartFormDataBuilderTest.java index 923d0c356a..3f34ceafc4 100644 --- a/modules/kernel/test/org/apache/axis2/builder/MultipartFormDataBuilderTest.java +++ b/modules/kernel/test/org/apache/axis2/builder/MultipartFormDataBuilderTest.java @@ -65,9 +65,9 @@ public class MultipartFormDataBuilderTest extends TestCase { * * <p>Worth stating why this test exists separately from * {@link RequestSizeLimitsTest}: that one covers parameter resolution, and - * the reporter's own proof-of-concept checks the limit by reconstructing its - * own upload object rather than going through {@code processDocument}, so - * neither actually demonstrates that an oversized body is refused. + * it is easy to check the limit by reconstructing an upload object rather + * than going through {@code processDocument}, which demonstrates nothing + * about whether an oversized body is actually refused. */ public void testOversizedRequestIsRejected() throws Exception { MessageContext messageContext = newMessageContext(buildBody("bigFile", "big.bin"));
