It's up to the client developer to figure out how to process the complex types. As an Axis service developer, you might consider providing class files for Java clients (a JavaBean to represent the complex type, the serializer routine, and maybe any exception routines), although I doubt that you would provide comparable files for other languages (e.g., VB, C#, etc).
If you want to provide the class files, you could register them in UDDI, although there's no standard convention for doing so. I'd create a taxonomy tModel to represent Java class files. Then create a tModel to represent each class file and categorize them as Java class files. (The keyValue attribute would indicate what type of class file you've supplied.) Have the overviewURL of each tModel point to the .jar file, and add tModelInstanceDetails elements in the bindingTemplate to point to the class file tModels. Anne ----- Original Message ----- From: "Agarwal, Naresh" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 11, 2003 8:23 AM Subject: question about supporting complex data type > Hi > > If we use some complex datatype (as parameter/return value) in one of the functions of a Web Service, which is deployed using AXIS, then the Web Service client would need the following apart from WSDL file: > > 1) class file for complex datatype > 2) class file for serializer and deserializer for the complex data type > > Where would Web Service clients get this from? > Do these reside at the same place as WSDL? > Does UDDI have any information about the location of these? > > thanks, > > regards, > Naresh Agarwal >
