Hi Rich,
thank you for pointing out the JSR - I had the same problem as Milos. I use Beta 3 and I have the problem, that an exception is thrown in my Axis-Client, when trying to analyze the SOAP fault message: I do not know, whether there is something wrong with my SOAP-Message (see below - it doesn't seem to be properly serialized - encoding is rpc) or whether the error is with the Axis-Client. SOAP-Code according to TCPMonitor: HTTP/1.1 500 Internal Server Error Content-Type: text/xml; charset=utf-8 Date: Thu, 18 Jul 2002 13:13:09 GMT Server: Apache Tomcat/4.0.1 (HTTP/1.1 Connector) Connection: close <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi ="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <soapenv:Fault> <faultcode xmlns:ns1 ="http://xml.apache.org/axis/";>ns1:server.MPSError</faultcode> <faultstring>null : Internal application error.</faultstring> <detail> <Provider>xyz</Provider> <ErrorCode>-8</ErrorCode> <ErrorMessage> user identity unknown: user_unknown</ErrorMessage> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> Exception on the Client-side: - Mapping Exception to AxisFault AxisFault faultCode: {http://xml.apache.org/axis/}server.MPSError faultString: null : Internal application error. faultActor: null faultDetail: Provider: xyz ErrorCode: -8 ErrorMessage: user identity unknown: user_unknown null : Internal application error. at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:135) at org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl.java:904) at org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403) at org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1180) at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1256) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:952) at javax.xml.parsers.SAXParser.parse(SAXParser.java:379) at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:213) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:457) at org.apache.axis.Message.getSOAPEnvelope(Message.java:362) at org.apache.axis.client.Call.invokeEngine(Call.java:2046) at org.apache.axis.client.Call.invoke(Call.java:2016) at org.apache.axis.client.Call.invoke(Call.java:1786) at org.apache.axis.client.Call.invoke(Call.java:1711) at org.apache.axis.client.Call.invoke(Call.java:1251) at com.varetis.ida.clients.webservices.MPS.generated.IdaMPSBindingStub.getCurrentPosition(IdaMPSBindingStub.java:249) at com.varetis.ida.Client.IdaMPSServiceFrame.callWebservice(IdaMPSServiceFrame.java:288) at com.varetis.ida.Client.IdaMPSServiceFrame$9.run(IdaMPSServiceFrame.java:230) Thanks a lot, Monika > [EMAIL PROTECTED] > 17.07.2002 16:02 > Please respond to axis-user > > To: [EMAIL PROTECTED] > cc: > Subject: Re: fault message > >See JSR 101 version 1.0 chapter 4.3.6 The mapping fo WSDL faults has >changed several times during the development of the specification. > >If you still think that the Axis is in error, please open a bugzilla >defect. > >Thanks, > >Rich 'Shirley' Scheuerle >IBM WebSphere & Axis Web Services Development >512-838-5115 (IBM TL 678-5115) > > > > >"Milos Cekovic" <[EMAIL PROTECTED]> >07/17/2002 04:02 AM >Please respond to axis-user > > > To: [EMAIL PROTECTED] > cc: > Subject: fault message > > > >Hi, > >In beta2 WSDL2Java generates for each fault in a portType a class that >extends AxisFault. This class is thrown from a service call. > >Since beta3 WSDL2Java does not generate this class. It just throws >a ComplexType that is a part of a fault message which results in >compilation >errors. > >Here is the portType definition: > ><portType name="SrvDataDictionaryPortType"> > <operation name="getDataDictionary"> > <input message="..."/> > <output name="..."/> > <fault name="getDataDictionaryException" message >="datadict:DataDictionaryFault"/> > </operation> >... > >And the message is: > ><message name="DataDictionaryFault"> > <part name="exception" type="mytypes:ArrayOfMyError"/> ></message> > >The array is defined as: > ><complexType name="ArrayOfMyError"> > <complexContent> > <restriction base="soapenc:Array"> > <sequence> > <element name="item" minOccurs="0" maxOccurs="unbounded" type >="mytypes:MyError"/> > </sequence> > <attribute ref="soapenc:arrayType" >soapenc:arrayType="mytypes:MyError >[]"/> > </restriction> > </complexContent> ></complexType> > >And its elements as: > ><complexType name="MyError"> > <all> > <element name="code" type="xsd:string"/> > <element name="message" type="xsd:string"/> > </all> ></complexType> > > >In beta2 WSDL2Java generated a DataDictionaryFault class that extends >AxisFault. >In beta3 there s no such class, but in PortType.java service throws it! > >Is it a bug in WSDL2Java? > >Do you have some workarounds? > >Thanks in advance. > >Milos Cekovic >Basel, Switzerland > > > > > > >
