Yes you are right Russel...I was apparently still referencing an an older
jar...my apologies.
Thanks for the quick reply,
David Cole
"Russell
Butek" To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
.com> Subject: Re: Problems with calendar in
generated wsdl
04/03/2002
11:59 AM
Please
respond to
axis-dev
I'm a bit puzzled. A few days ago I updated the AXIS mappings to reflect
JAX-RPC, which says java.util.Calendar maps to xsd:dateTime. So if you ran
your classes through Java2WSDL in the last couple days, you shouldn't have
seen ANY calendar entries, just xsd:dateTime entries.
Russell Butek
[EMAIL PROTECTED]
"David L. Cole" <[EMAIL PROTECTED]> on 04/03/2002 11:26:46 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Problems with calendar in generated wsdl
Using the Java2WSDL tool, I am getting an inconsistency in the generated
WSDL file for java.util.Calendar
Attached is the generated WSDL. and the service class and a couple of
Objects represented within the WSDL
(See attached file: AssociateService.java)(See attached file: service.wsdl)
(See attached file: Contact.java)(See attached file: ContactData.java)
The inconsistency comes from comparing the messages vs. complex type
declarations, for example:
<wsdl:message name="getDefaultContactRequest">
<wsdl:part name="in0" type="xsd:int"/>
<wsdl:part name="in1" type="tns4:BusinessAssociateOID"/>
<wsdl:part name="in2" type="SOAP-ENC:string"/>
<wsdl:part name="in3" type="tns2:Calendar"/>
</wsdl:message>
Shows the Calendar reference mapped to namespace 'tns2'
While the complex type:
<complexType abstract="true" name="Contact">
<sequence>
<element name="EffBeginDt" nillable="true" type="xsd:Calendar"/>
<element name="EffEndDt" nillable="true" type="xsd:Calendar"/>
<element name="UpdateDt" nillable="true" type="xsd:Calendar"/>
<element name="Updater" nillable="true" type="xsd:string"/>
<element name="ContactId" nillable="true" type="SOAP-ENC:int"/>
<element name="NamePrefix" nillable="true" type="xsd:string"/>
<element name="FirstName" nillable="true" type="xsd:string"/>
<element name="Nickname" nillable="true" type="xsd:string"/>
<element name="MiddleInit" nillable="true" type="xsd:string"/>
<element name="LastName" nillable="true" type="xsd:string"/>
<element name="NameSuffix" nillable="true" type="xsd:string"/>
<element name="CorpClientInd" nillable="true" type="xsd:string"/>
<element name="LoginName" nillable="true" type="xsd:string"/>
<element name="RecNewsLetterFlag" nillable="true" type="xsd:string"/>
<element name="ViewProfileFlag" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
Shows the Calendar mapped to the default namespace 'xsd'.
What is the correct mapping and namespace for Calendar?
I am currently using the latest nightly build as of 4/3/2001 when getting
this error.
(This error also occurs in the beta version)
Thanks,
David Cole
