Re: [sca-bindings] NEW ISSUE: Testing experience suggests requirementsBWS40002 & BWS40003 are too strict for services

[Bryan Aupperle <aupperle@us.ibm.com>]

Mike,
    when you were trying to
force a service to only receive messages using SOAPI 1.2, what happened
if the only binding in the WSDL had a <SOAP:binding/> element with
the transport attribute set to the SOAP 1.2 URL (http://www.w3.org/2003/05/soap/bindings/HTTP/)?

I think you can control this using the
JAX-WS @BindingType annotation.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of
Excellence Application Integration Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

From:	Eric Johnson <eric@tibco.com>
To:	OASIS SCA Bindings <sca-bindings@lists.oasis-open.org>
Date:	06/17/2010 06:59 PM
Subject:	[sca-bindings] NEW ISSUE: Testing experience suggests requirements BWS40002 & BWS40003 are too strict for services

---

Target: sca-wsbinding-1.1-spec-cd03

Title: Testing experience suggests requirements BWS40002 & BWS40003
are
too strict for services

Description:

Current normative statements:

When the SOAP.1_1 intent is required, the SCA runtime MUST transmit and
receive messages using only SOAP 1.1. [BWS40002]

When the SOAP.1_2 intent is required, the SCA runtime MUST transmit and
receive messages using only SOAP 1.2. [BWS40003]

Mike Edward's experience in creating test cases suggests that at least
two existing implementations (Axis, JAX-WS reference implementation) of
SOAP stacks will gladly accept SOAP 1.1 or SOAP 1.2 at a given endpoint,
and that restricting them to only allowing SOAP 1.1 or SOAP 1.2 is
actually tricky, if it is even possible.

This suggests that the normative statements, when applied to *services*
are perhaps overly strict.  Note that it still makes sense to have
these
policy intents on references.

Proposal:

Change the normative statements to read as follows:
When the SOAP.1_1 intent is required on a reference, the SCA runtime
MUST transmit and receive messages using only SOAP 1.1. [BWS40002]

When the SOAP.1_2 intent is required on a reference, the SCA runtime
MUST transmit and receive messages using only SOAP 1.2. [BWS40003]



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php