Jeff Greif wrote:

WSIF definitely supports <schema> in the <types> section of the WSDL
document, without any special additions. Probably something else in the
wsdl is causing the UnknownExtensibilityElement problem. Perhaps you can
tell by looking at the wsdls for the WSIF samples, or by providing some more
details to this list.


Kiran,

i am a bit suspicious of "http://www.w3.org/1999/XMLSchema";

i think it should be "http://www.w3.org/2001/XMLSchema"; ...

HTH,

alek

----- Original Message ----- From: "kiran" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, February 02, 2005 5:26 AM
Subject: XSD schema support in WSIF





Hi All,

Is WSIF support the XSD types?
I want to read(create also) the following WSDL, also need to read the
associated XSD types and elements.
How can I achive this?
When I try reading tehis, I get UnknownExtensionsibilityElement- Is
there are ExtensibilityElement avaialbale for XSD schema?
--------------------------A part of the WSDL-------------
<definitions  .....>
<!-- type defs -->
<types>
   <xsd:schema
     targetNamespace="http://wsiftypes.addressbook.service.ejb/";
               xmlns:xsd="http://www.w3.org/1999/XMLSchema";>
     <xsd:complexType name="phone">
       <xsd:sequence>
         <xsd:element name="areaCode" type="xsd:int"/>
         <xsd:element name="exchange" type="xsd:string"/>
         <xsd:element name="number" type="xsd:string"/>
       </xsd:sequence>
     </xsd:complexType>

     <xsd:complexType name="address">
       <xsd:sequence>
         <xsd:element name="streetNum" type="xsd:int"/>
         <xsd:element name="streetName" type="xsd:string"/>
         <xsd:element name="city" type="xsd:string"/>
         <xsd:element name="state" type="xsd:string"/>
         <xsd:element name="zip" type="xsd:int"/>
         <xsd:element name="phoneNumber" type="typens:phone"/>
       </xsd:sequence>
     </xsd:complexType>
   </xsd:schema>
 </types>

 <!-- message declns -->
 <message name="AddEntryWholeNameRequestMessage">
   <part name="name" type="xsd:string"/>
   <part name="address" type="typens:address"/>
 </message>

<message name="AddEntryFirstAndLastNamesRequestMessage">
<part name="firstName" type="xsd:string"/>
<part name="lastName" type="xsd:string"/>
<part name="address" type="typens:address"/>
</message>
...
------------------------------







--
The best way to predict the future is to invent it - Alan Kay



Reply via email to