This is an automated email from the ASF dual-hosted git repository.
veithen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ws-axiom.git
The following commit(s) were added to refs/heads/master by this push:
new 80b946499 List non-deprecated methods that still declare
XMLStreamException without StAX interaction
80b946499 is described below
commit 80b9464997961ff7f9f072c4b6ef1e6b5b566dce
Author: Andreas Veithen-Knowles <[email protected]>
AuthorDate: Sun Feb 22 08:07:12 2026 +0000
List non-deprecated methods that still declare XMLStreamException without
StAX interaction
---
docs/roadmap.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/docs/roadmap.md b/docs/roadmap.md
index c49a941c0..c36a69e78 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -51,7 +51,12 @@ Axiom 1.3 to meet the following requirements:
* As noted in [ADR 0003](adr/0003-no-stax-assumption-in-api.md), the Axiom
API should not be
designed around the assumption that StAX is used as the XML parser.
Therefore methods defined
by the Axiom API should only declare `XMLStreamException` if they interact
directly with a
- StAX object supplied by application code.
+ StAX object supplied by application code. The following non-deprecated
methods still violate
+ this principle:
+
+ * `OMElement.toStringWithConsume()`
+ * `AXIOMUtil.stringToOM(String)`
+ * `AXIOMUtil.stringToOM(OMFactory, String)`
* Axiom should have well-defined (and distinct) exceptions for at least the
following two error cases:
