Based on your schema, the fault message should look like this:
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Some message</faultstring>
<detail>
<n1:MyException xmlns:n1="http://MyNamespace">
<ns1:mesg1 xsi:nil="true"></ns1:mesg1>
<ns1:mesg2 xsi:nil="true"></ns1:mesg2>
</n1:MyExceptio>
</detail>
</env:Fault>
Also, please verify that you have in fact defined an *element*. (The
schema fragment you showed us only defines a complex type.)
Make sure that this declaration is included in your schema:
<xsd:element name="MyException" type="tns:MyException"/>
And make sure your WSDL fault message part references this element.
Anne
On 6/11/07, Ali, Haneef <[EMAIL PROTECTED]> wrote:
Hi,
I have the following complex Element
<xsd:schema elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://MyNamespace">
<xsd:complexType name="MyException">
<xsd:sequence>
<element name="mesg1" type="xsd:string" />
<element name="mesg2" type="xsd:string" />
</xsd:sequence>
<xsd:complexType>
<xsd:schema>
I have omitted unnecessary implementation details. Bascially my weblogic
webservice throws this excecption and the xml in the wire look like
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Some message</faultstring>
<detail>
<n1:MyException xmlns:n1="http://MyNamespace">
<mesg1 xsi:nil="true"></mesg1>
<mesg2 xsi:nil="true"></mesg2>
</n1:MyExceptio>
</detail>
</env:Fault>
This xml fragment is accepted by both Axis 1.4 client and weblogic
client. Axis 2.0 rejects this. Axis 2.0 is not able to findout the
namespace for the element "mesg1' and "mesg2".
Can you please let me know who is correct? I believe Axis2.0 is correct
Thanks,
Haneef
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]