Hi Kim,
I dont't know how to define interfaces but you could define "abstract" supertypes in your wsdl. Axis then generates an abstract class for that type.
Here's an example:
<s:complexType name="RequestBaseType" abstract="true">
</s:complexType>
<s:complexType name="RequestType">
<s:complexContent>
<s:extension base="s:RequestBaseType">
<!-- define your attributes/elements here -->
</s:extension>
</s:/complexContent>
</s:complexType>
RequestType is a subtype of RequestBaseType. So you could use the "interface" RequestBaseType anywhere in your code, where you actually deal with a RequestType.
Matthias.
-----Original Message-----
From: Quinn, Kim John [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 16, 2002 12:28 AM
To: '[EMAIL PROTECTED]'
Subject: Defining Interfaces in WSDL?
Importance: High
Hey all, well - im past deserializing now but have a new question to bang my head against...
Has anyone defined a WSDL document that uses "interfaces?"
What I need to do (due to code that uses it) is have my WebService work with the interfaces as the types as opposed to the implementations. Its either that or it seems like I am going to have to create proxy's for every single one...
Any suggestions or pointers to where I could find a sample would be great!
Thanks.
KJQ
