[
http://issues.apache.org/jira/browse/AXIS-1903?page=comments#action_65131 ]
Joaquim Rocha commented on AXIS-1903:
-------------------------------------
I'm having the same problem with WebLogic 8.1 and Axis 1.2 (final).
####<May 12, 2005 3:51:21 PM WEST> <Info> <EJB> <teste> <server1>
<ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<anony
mous>> <> <BEA-010051> <EJB Exception occurred during invocation from home:
[EMAIL PROTECTED]
8eccf5 threw exception: java.lang.IncompatibleClassChangeError
java.lang.IncompatibleClassChangeError
at
org.apache.axis.message.MessageElement.addTextNode(MessageElement.java:1387)
at org.apache.axis.message.SOAPHandler.addTextNode(SOAPHandler.java:148)
at org.apache.axis.message.SOAPHandler.endElement(SOAPHandler.java:112)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
weblogic.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:585)
at
weblogic.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(XMLNamespaceBinder.java:898)
at
weblogic.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java:644)
at
weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1008)
at
weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerI
mpl.java:1469)
at
weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at
weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:152)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:784)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
...
> IncompatibleClassChangeError when deploying Axis 1.2-RC3 on WebSphere 5.1
> with PARENT_FIRST classloading
> --------------------------------------------------------------------------------------------------------
>
> Key: AXIS-1903
> URL: http://issues.apache.org/jira/browse/AXIS-1903
> Project: Axis
> Type: Bug
> Components: SAAJ
> Versions: 1.2RC3
> Environment: WebSphere 5.1.x on Linux (2.4.x kernel).
> Reporter: David Tompkins
>
> I am deploying Axis 1.2RC3 in a war that resides within an ear. The axis jars
> are in the war/WEB-INF/lib dir. For various reasons related to the other
> contents of my ear, I must use PARENT_FIRST classloading. As many have
> reported, if you have PARENT_FIRST classloading on WebSphere 5.1 with Axis
> 1.2RC3, then there is a conflict between the version of saaj (1.1) that ships
> with WebSphere, and the version of saaj (1.2) that Axis 1.2RC3 expects, and
> you get the following exception:
>
> java.lang.IncompatibleClassChangeError: class org.apache.axis.SOAPPart does
> not implement interface org.w3c.dom.Document
>
> This issue can be resolved with PARENT_LAST classloading and a manifest which
> specifies the classpath...but for those of use who can't use PARENT_LAST
> classloading, there is another option.
>
> It appears that a single source code change to Axis will eliminate the issue
> altogether. The offending code is in
> org.apache.axis.message.MessageElement.addTextNode(), and can be patched as
> follows:
>
> OLD CODE:
>
> public SOAPElement addTextNode(String s) throws SOAPException {
> try {
> Text text = getOwnerDocument().createTextNode(s);
> ((org.apache.axis.message.Text)text).setParentElement(this);
> return this;
> } catch (ClassCastException e) {
> throw new SOAPException(e);
> }
> }
>
> PATCHED CODE:
>
> public SOAPElement addTextNode(String s) throws SOAPException {
> try {
> Text text = new org.apache.axis.message.Text(s);
> this.appendChild(text);
> return this;
> } catch (ClassCastException e) {
> throw new SOAPException(e);
> }
>
> After making this change, Axis 1.2RC3 will run on WebSphere 5.1 with
> PARENT_FIRST classloading, and no exceptions will be thrown.
>
> -DT
>
> ---------------------------------
> David Tompkins
> Sr. Computer Scientist
> Adobe Systems, Inc.
> tompkins _AT_ adobe _DOT_ com
> http://www.dt.org/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
