cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-3328) Improve WS-I Basic Profile conformance
Date Fri, 11 Feb 2011 15:41:57 GMT

    [ https://issues.apache.org/jira/browse/CXF-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993543#comment-12993543
] 

Glen Mazza commented on CXF-3328:
---------------------------------

The JAX-WS specification (here, the Java-to-WSDL mapping) is what CXF must implement, even
if it allows users to violate the WS-I Basic Profile requirements.  For example R2710 violations
are going to happen if the developer chooses construct his Java class to create those situations,
same with many other of the Basic Profile rules.  Choosing to follow the WS-I Basic Profile
is the prerogative of the developer, JAX-WS does not require you to follow WS-I Basic Profile.
 In other words, what you're asking us to do is akin to asking Microsoft Word developers to
prohibit typing of double negatives or split infinitives.

The WS-I maintains tools to make sure your WSDLs are "legit" w.r.t. the Basic Profiles, tools
that can be used regardless of web service stack (CXF or Metro or other) you're using, so
I don't see a need for CXF to duplicate this effort.  However, if there are specific Java-to-WSDL
changes CXF can make that don't violate the JAX-WS spec and would remove a WS-I basic profile
violation, that would be a good idea for us to consider.

> Improve WS-I Basic Profile conformance
> --------------------------------------
>
>                 Key: CXF-3328
>                 URL: https://issues.apache.org/jira/browse/CXF-3328
>             Project: CXF
>          Issue Type: Improvement
>          Components: Soap Binding
>    Affects Versions: 2.3.1
>            Reporter: Dennis Kieselhorst
>
> The auto-generated wsdls currently violate the following WS-I Basic Profile requirements:
> * BP2012: R2204 A document-literal binding in a DESCRIPTION MUST refer, in each of its
wsoap11:body element(s), only to wsdl:part element(s) that have been defined using the element
attribute (http://ws-i.org/Profiles/BasicProfile-1.2-2010-11-09.html#BP2012).
> * BP2101: R2001 A DESCRIPTION MUST only use the WSDL "import" statement to import another
WSDL description (http://ws-i.org/Profiles/BasicProfile-1.2-2010-11-09.html#BP2101).
> * BP2119: R2210 If a document-literal binding in a DESCRIPTION does not specify the parts
attribute on a wsoap11:body element, the corresponding abstract wsdl:message MUST define zero
or one wsdl:parts (http://ws-i.org/Profiles/BasicProfile-1.2-2010-11-09.html#BP2119).
> * BP2120a: R2710 The operations in a wsdl:binding in a DESCRIPTION MUST result in operation
signatures that are different from one another (http://ws-i.org/Profiles/BasicProfile-1.2-2010-11-09.html#BP2120a).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message