Mr Cliffe. I have observed that in the wsdl file generated for my java class the xsd:type doesn't change once created!
for example if i have created a method which returns String then recompile the class to a int method, then the xsd:..type doenst change it is string by default, looks mysterious. is my problem also similar to yours..? From: "Owen Cliffe" <[EMAIL PROTECTED] default ic.uk> To: <[EMAIL PROTECTED]> Sent: Sunday, December 01, 2002 7:56 PM Subject: WSDL autogeneration of non-visible classes > Hi, apologies if this is a duplicate, there are mail issues. > > Is there a way of explicitly telling axis to include certain classes in > the WSDL type definition without them being exposed through parameters or > return types of available service methods? > > we have been successfully using axis to automatically generate WSDL from > our interface data classes, however we have come to a problem caused by > the fact that our data classes use java.util.List type classes which > obviously hide the type of the classes contained in those lists such that > the BeanGenerator correctly cannot determine that type for WSDL > generation (and inserts an xsd:anytpye) > > Having looked at the documentation and specifically about WSDD i have been > unable to glean any more useful information. > > at present we are cheating by creating dummy methods in our service which > use the classes that are not already being generated . > > -- > Owen Cliffe, Ph.D. Student, Dept. Computer Science > University of Bath > > > -- > Owen Cliffe, Ph.D. Student, Dept. Computer Science > University of Bath > > >
