SERVICES 

Hi!

In my opinion this kind of WSDL is perfectly legal. But it is 
uncommon and it is not good practice. 

Look into WSDL 1.1 specification and/or WS-I Basic Profile 1.1. They 
do not prevent you from doing that. 

Merging of that two schemas could be solution. Problem arise when e.g 
one schema different elementFromDefault to the second one... But I 
hope this is only a theory ;)

Milan Boruvka

--- In soapbuilders@[...].com, "jeehongmin2003" 
<jeehongmin2003@[...]..>  wrote:
>  Recently, I have been seeing multiple inlined schemas with the same
>  namespace in our customers' WSDLs.  For example (ignoring 
namespaces):
>  
>  <wsdl:definition>
>  <wsdl:types>
>  <xs:schema targetNamespace="a">
>  types and elements
>  </xs:schema>
>  <xs:schema targetNamespace="a">
>  different types and elements
>  </xs:schema>
>  <xs:schema targetNamespace="b">
>  whatever
>  </xs:schema>
>  </wsdl:types>
>  ...
>  <wsdl:definition>
>  
>  My understanding is that each inlined schema should have a unique
>  namespace.  So what I've done is merge the two schemas with
>  targetNamespace="a".  
>  
>  Am I correct in concluding that the above WSDL is incorrect?  If so,
>  why are various WSDL generators allowing that?
>  
>  Thanks,
>  
>  Jeehong Min





------------------------ Yahoo! Groups Sponsor --------------------~-->  
$9.95 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/W6uqlB/TM
--------------------------------------------------------------------~->  

-----------------------------------------------------------------
This group is a forum for builders of SOAP implementations to discuss implementation and int
eroperability issues.  Please stay on-topic. 
Yahoo! Groups Links

<*>  To visit your group on the web, go to:
    http://groups.yahoo.com/group/soapbuilders/

<*>  To unsubscribe from this group, send an email to:
    soapbuilders-unsubscribe@[...].com

<*>  Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/