Apparently, there is some cases where when a DOMSource is converted to a SOAPBody by the SOAP BC using the Axiom library (from Petals to the outside thus), Axiom fails to do so.
The (temporary) solution is thus to convert the DOMSource to a ByteSource before (i.e. the Document is parsed by the Java library code and not by Axiom and then it is transformed to a stream read by Axiom).
Apparently, there is some cases where when a DOMSource is converted to a SOAPBody by the SOAP BC using the Axiom library (from Petals to the outside thus), Axiom fails to do so.
The bug is reported there: https://issues.apache.org/jira/browse/AXIOM-487
The (temporary) solution is thus to convert the DOMSource to a ByteSource before (i.e. the Document is parsed by the Java library code and not by Axiom and then it is transformed to a stream read by Axiom).
Christophe DENEUX added a comment - Thu, 30 Mar 2023 - 16:11:08 +0200
As the initial problem (AXIOM-487) is fixed in Axiom 1.3.0. We can remove the workaround upgrading Axis2 to 1.8.2 because this version of Axis2 is coming with Axiom 1.4
Christophe DENEUX added a comment - Thu, 30 Mar 2023 - 16:11:08 +0200 As the initial problem (AXIOM-487) is fixed in Axiom 1.3.0. We can remove the workaround upgrading Axis2 to 1.8.2 because this version of Axis2 is coming with Axiom 1.4
Workaround removed in version 5.1.0