I have an interface with a method that looks something like this: =====
public interface Foo { public boolean isBar( String fooName, java.util.Calendar startDate, java.util.Calendar endDate); } ===== I have successfully deployed an implementation of this interface by using a .wsdd file. However, the resulting wsdl file maps startDate and endDate to xsd:dateTime types. Since startDate and endDate are dates, and not date/times, I would prefer mapping them to xsd:date types. To do so, I have rummaged through the documentation and come up with the following somewhat likely looking .wsdd file: ===== <deployment xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"> <service name="Foo" provider="java:RPC"> <parameter name="baseClassName" value="com.intimesoft.Foo"/> <parameter name="className" value="com.intimesoft.FooImpl"/> <parameter name="scope" value="application" /> <parameter name="allowedMethods" value="*"/> <operation name="isBar" > <parameter name="fooName" type="xsd:string"/> <parameter name="startDate" type="xsd:date"/> <parameter name="endDate" type="xsd:date"/> </operation> </service> </deployment> ====== The problem is, it doesn't work. The resultant .wsdl file still specifies "xsd:dateTime" types for both the startDate and endDate parameters. At the risk of sounding like an idiot, what am I missing? Or is this something I can only accomplish by starting with a .wsdl file and working backwards? Jeff 8-)