I'm not sure what the problem is.  Is it that the wsdlvalidator doesn't test
all WS-I rules?  Yes, that's certainly correct, probably just a small subset
it checks.  Please enter JIRA enhancement requests and/or patches to make it
more rigorous.

Also note CXF implements the JAX-WS specification, not the WS-I one.  It
will include those portions of JAX-WS that WS-I would complain about.  By
definition, anything implementing JAX-WS will violate the WS-I suggestions,
because the latter defines the subset of allowable JAX-WS functionality that
a web service provider should use.  Following WS-I is advisable but still
optional, and more the responsibility of the developer than the web service
stack.

Glen 


Andrea Poli-2 wrote:
> 
> Hi,
> 
> I need some explanation about the wsdl validator and wsdl2java generator 
> tools (cxf/bin, versione 2.2.7).
> The tool wsdlvalidator doesn't generate error for the wsdl in attach.
> 
> Here are some BP1.1 statements (4.7.11Consistency of portType and 
> binding Elements):
> "R2718 A |wsdl:binding| in a DESCRIPTION MUST have the same set of | 
> wsdl:operation|s as the |wsdl:portType| to which it refers."
> 
> It's correct that wsdl tools (cxf/bin/wsdl2java and 
> cxf/bin/wsdlvalidator) accept WSDL in attach ?
> I expect me for an R2718 violation.
> 
> Andrea Poli
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <xs:schema elementFormDefault="qualified"
>       targetNamespace="http://www.link.it/spcoop_java_architect/beans";
> xmlns:ns="http://www.link.it/spcoop_java_architect/beans";
>       xmlns:xs="http://www.w3.org/2001/XMLSchema";
> xmlns:jaxb="http://java.sun.com/xml/ns/jaxb";
>       xmlns:wsi="http://ws-i.org/profiles/basic/1.1/xsd";
>       jaxb:version="2.0">
> 
>       
> 
>       <!-- OperationA (I/O) -->
>         <xs:element name="operationA">
>              <xs:complexType>
>                     <xs:sequence>
>                                   <xs:element name="test" type="xs:string"
>                                           minOccurs="1" maxOccurs="1" />
>                           </xs:sequence>
>                   </xs:complexType>
>         </xs:element>
>         <xs:element name="operationAResponse">
>              <xs:complexType>
>                       <xs:sequence>
>                               <xs:element name="esitoServizio" type="xs:int"
>                                       minOccurs="1" maxOccurs="1" />
>                       </xs:sequence>
>              </xs:complexType>
>         </xs:element>
> 
> 
>     <!-- OperationA (I/O) -->
>     <xs:element name="operationB">
>         <xs:complexType>
>             <xs:sequence>
>                 <xs:element name="test" type="xs:string"
>                     minOccurs="1" maxOccurs="1" />
>             </xs:sequence>
>         </xs:complexType>
>     </xs:element>
>     <xs:element name="operationBResponse">
>         <xs:complexType>
>             <xs:sequence>
>                 <xs:element name="esitoServizio" type="xs:int"
>                     minOccurs="1" maxOccurs="1" />
>             </xs:sequence>
>         </xs:complexType>
>     </xs:element>
> 
> </xs:schema>
> 
>  
> 

-- 
View this message in context: 
http://old.nabble.com/WSDL-Validator-and-WS-BS-1.1-R2718-tp28328955p28329297.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to