Hi,
We're having an issue where we have a saxon jar on the classpath of our
application (we cannot get around doing this as it's used in other parts of the
application), and we're trying to use apache axis to connect to the server.
We're seeing a good number of the following exceptions:
2011-04-25 00:06:03,007 [WebContainer : 4] DEBUG org.apache.axis.enterprise -
Mapping Exception to AxisFault
java.lang.UnsupportedOperationException: The Saxon DOM cannot be updated
at
com.icl.saxon.om.AbstractNode.disallowUpdate(AbstractNode.java:609)
at
com.icl.saxon.om.AbstractNode.createElementNS(AbstractNode.java:805)
at
org.apache.axis.utils.XMLUtils.StringToElement(XMLUtils.java:524)
at org.apache.axis.AxisFault.addFaultDetail(AxisFault.java:657)
at
org.apache.axis.AxisFault.initFromException(AxisFault.java:272)
at org.apache.axis.AxisFault.<init>(AxisFault.java:205)
at org.apache.axis.client.Call.invokeEngine(Call.java:2826)
at org.apache.axis.client.Call.invoke(Call.java:2797)
at org.apache.axis.client.Call.invoke(Call.java:2473)
at org.apache.axis.client.Call.invoke(Call.java:2396)
at org.apache.axis.client.Call.invoke(Call.java:1816)
Seems like when it's trying to create an AxisFault exception, it's failing due
to saxon returning a 'TinyDocumentImpl' when creating a doc through the saxon
DocumentBuilderImpl.newDocument().
Is there any way to change the XML parser *just* for axis?
We're currently using axis v1.4. Is there any fix for this issue in axis2?
Thanks and regards,
Justin
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
