You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Ha...@newyorklife.com on 2003/09/04 04:23:38 UTC

java.lang.IllegalArgumentException

Hi,
      I'm receiving following soap exception in my .NET client from Axis.

<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>soapenv:Server.userException</faultcode>
   <faultstring>java.lang.IllegalArgumentException:
java.lang.ClassCastException@e637f0</faultstring>
   <detail/>
  </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>

      Here is partial WSDL file.

      <complexType name="TestSchedule">
            <sequence>
                <element name="executed" type="xsd:boolean" />
                <element name="executionTime" nillable="true" type="
              xsd:anyType" />
                <element name="fileName" nillable="true" type="xsd:string"
              />
                <element name="id" nillable="true" type="xsd:long" />
                <element name="project" nillable="true" type="tns1:Project"
              />
                <element name="targetApp" nillable="true" type="xsd:string"
              />
                <element name="targetAppVersion" nillable="true" type="
              xsd:string" />
                <element name="targetServer" nillable="true" type="
              xsd:string" />
                <element name="testListXML" nillable="true" type="
              xsd:string" />
              </sequence>
          </complexType>
        <complexType name="Project">
            <sequence>
                <element name="id" nillable="true" type="xsd:long" />
                <element name="projectName" nillable="true" type="
              xsd:string" />
            </sequence>
          </complexType>

        The field executionTime is defined as Timestamp type and I'm using
        a DateTime object in my .NET client. Has anyone run into this type
        of interop problem? If yes, any work around? Thanks.

        Harry Wen