Test
Assertions for the SCA Web Service Binding Version 1.1 Specification
Committee
Draft 01 / Public Review 01
1 July
2010
Specification
URIs:
This
Version:
http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-test-assertions-cd01.html
http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-test-assertions-cd01.odt
http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-test-assertions-cd01.pdf
(Authoritative)
Previous
Version:
N/A
Latest
Version:
http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-test-assertions.html
http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-test-assertions.odt
http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-test-assertions.pdf
(Authoritative)
Technical
Committee:
OASIS
Service Component Architecture / Bindings (SCA-Bindings) TC
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-bindings
Chair(s):
Simon
Holdsworth, IBM
Editor(s):
Anish
Karmarkar, Oracle
Mike
Edwards, IBM
Related
Work:
This
specification is related to:
·
Service Component Architecture Web
Service Binding Specification Version 1.1
http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-spec-cd04.pdf
Declared
XML Namespace(s):
None
Abstract:
This document defines the Test
Assertions for the SCA Web Service Binding specification.
The Test Assertions represent the testable items relating to the normative
statements made in the SCA Assembly specification. The Test Assertions provide a bridge between
the normative statements in the specification and the conformance TestCases
which are designed to check that an SCA runtime conforms to the requirements of
the specification.
Status:
This
document was last revised or approved by the OASIS Service Component
Architecture / Bindings (SCA-Bindings) TC on the above
date. The level of approval is also listed above. Check the "Latest
Version" or "Latest Approved Version" location noted above for
possible later revisions of this document.
Technical
Committee members should send comments on this specification to the Technical
Committee’s email list. Others should send comments to the Technical Committee
by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/sca-bindings/.
For
information on whether any patents have been disclosed that may be essential to
implementing this specification, and any offers of patent licensing terms,
please refer to the Intellectual Property Rights section of the Technical
Committee web page (http://www.oasis-open.org/committees/sca-bindings/ipr.php).
The
non-normative errata page for this specification is located at http://www.oasis-open.org/committees/sca-bindings/.
Copyright © OASIS® 2009,
2010. All Rights Reserved.
All
capitalized terms in the following text have the meanings assigned to them in
the OASIS Intellectualoperty Rights Policy (the "OASIS IPR Policy").
The full Policy may be found at the OASIS website.
This
document and translations of it may be copied and furnished to others, and
derivative works that comment on or otherwise explain it or assist in its
implementation may be prepared, copied, published, and distributed, in whole or
in part, without restriction of any kind, provided that the above copyright
notice and this section are included on all such copies and derivative works.
However, this document itself may not be modified in any way, including by
removing the copyright notice or references to OASIS, except as needed for the
purpose of developing any document or deliverable produced by an OASIS
Technical Committee (in which case the rules applicable to copyrights, as set
forth in the OASIS IPR Policy, must be followed) or as required to translate it
into languages other than English.
The
limited permissions granted above are perpetual and will not be revoked by
OASIS or its successors or assigns.
This
document and the information contained herein is provided on an "AS
IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS
requests that any OASIS Party or any other party that believes it has patent
claims that would necessarily be infringed by implementations of this OASIS
Committee Specification or OASIS Standard, to notify OASIS TC Administrator and
provide an indication of its willingness to grant patent licenses to such
patent claims in a manner consistent with the IPR Mode of the OASIS Technical
Committee that produced this specification.
OASIS
invites any party to contact the OASIS TC Administrator if it is aware of a
claim of ownership of any patent claims that would necessarily be infringed by
implementations of this specification by a patent holder that is not willing to
provide a license to such patent claims in a manner consistent with the IPR
Mode of the OASIS Technical Committee that produced this specification. OASIS
may include such claims on its website, but disclaims any obligation to do so.
OASIS
takes no position regarding the validity or scope of any intellectual property
or other rights that might be claimed to pertain to the implementation or use
of the technology described in this document or the extent to which any license
under such rights might or might not be available; neither does it represent
that it has made any effort to identify any such rights. Information on OASIS'
procedures with respect to rights in any document or deliverable produced by an
OASIS Technical Committee can be found on the OASIS website. Copies of claims
of rights made available for publication and any assurances of licenses to be
made available, or the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or users of
this OASIS Committee Specification or OASIS Standard, can be obtained from the
OASIS TC Administrator. OASIS makes no representation that any information or
list of intellectual property rights will at any time be complete, or that any
claims in such list are, in fact, Essential Claims.
The
names "OASIS", “SCA”, and “Service Component Architecture” are
trademarks of OASIS, the owner and
developer of this specification, and should be used only to refer to the
organization and its official outputs. OASIS welcomes reference to, and
implementation and use of, specifications, while reserving the right to enforce
its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php
for above guidance.
Table
of Contents
1
Introduction..................................................................................................................................... 5
1.1 Example Test
Assertion............................................................................................................. 5
1.2 Terminology.............................................................................................................................. 5
1.3 Normative
References............................................................................................................... 6
2 Test Assertions................................................................................................................................ 7
2.1 Section 2 Test
Assertions.......................................................................................................... 7
2.2 Section 4 Test
Assertions........................................................................................................ 17
2.3 Section 5 Test
Assertions........................................................................................................ 19
3 Cross Mapping of
Conformance Statements to Assertions.............................................................. 23
4 Conformance................................................................................................................................. 25
Appendix
A.Acknowledgments.......................................................................................................... 26
Appendix B.Revision
History............................................................................................................. 27
This document
defines the Test Assertions for the SCA Web Service Binding Specification
Version 1.1 [SCA-WSBinding].
The test assertions
in this document follow the format defined in the OASIS Test Assertion
Guidelines specification [TA-GUIDE].
1.1 Example Test Assertion
Test assertions are presented in a tabular format with rows
corresponding to the entry types defined in [TA-GUIDE].
|
Assertion ID
|
BWS-TA-xxxx
|
|
Source
|
[BWSyyyyy]
|
|
Target
|
<kitchenSink/> element of composite file
|
|
Prerequisites
|
The <kitchenSink/> element has a @drain attribute
|
|
Predicate
|
The @drain attribute value of the <kitchenSink/> element is a URI
that identifies a portal into the sewage system of the Domain.
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
kitchenSink drain sewage
|
Assertion ID: Is
a unique ID for the test assertion. Its format starts with a 3 letter string
that identifies the specification to which it relates - "BWS" is for
the SCA Web Service Binding specification.
This is followed by "-TA-" to indicate that this identifier is
for a test assertion. This is then followed
by a unique 4 digit number.
Source: Is the identifier(s) of the normative
statement(s) in the specification to which this assertion relates.
Target: Identifies the target which is addressed by
this assertion. This is typically some
SCA document element, or other SCA artifact but possibly could identify an SCA
runtime and its behaviour.
Prerequisites: Defines any prerquisites for this test
assertion. The prerequisites may be
defined in terms of one or more other test assertions that must be true.
Predicate: The meat of the assertion - something that
should evaluate to true or false for the given target.
Prescription Level: Mandatory (for MUST requirements) or Preferred
(for SHOULD requirements) or Permitted (for MAY requirements).
Tags: Zero or more labels that may be attached to
this test assertion - these tags can be used to group sets of assertions.
1.2
Terminology
The keywords "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",
"MAY", and "OPTIONAL" in this specification are to be
interpreted as described in IETF RFC 2119 [RFC
2119].
1.3 Normative References
[RFC 2119] S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. IETF RFC
2119, March 1997.
http://www.ietf.org/rfc/rfc2119.txt.
[TA-GUIDE] OASIS Committee Draft 04, Test Assertion Guidelines, February
2010. http://docs.oasis-open.org/tag/guidelines/v1.0/cd04/testassertionsguidelines-cd-04.pdf
[SCA-WSBinding] OASIS Committee Draft 04, “Service Component Architecture Web Service
Binding Specification Version 1.1,” May 2010.
http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-spec-cd04.pdf
2.1 Section 2 Test Assertions
|
Assertion ID
|
BWS-TA-20001
|
|
Source
|
[BWS20001]
|
|
Target
|
The reference/binding.ws/@uri attribute
|
|
Prerequisites
|
|
|
Predicate
|
The value of the attribute is an absolute value
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“uri attribute” “reference target”
|
|
Assertion ID
|
BWS-TA-20002
|
|
Source
|
[BWS20002]
|
|
Target
|
The binding.ws/@wsdlElement attribute
|
|
Prerequisites
|
|
|
Predicate
|
The value of the attribute points to an existing WSDL 1.1 element
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Assertion ID
|
BWS-TA-20003
|
|
Source
|
[BWS20003]
|
|
Target
|
The service/binding.ws/@wsdlEelement attribute
|
|
Prerequisites
|
|
|
Predicate
|
The value of the attribute is not of the form
<WSDL-namespace-URI>#wsdl.service(<service-name>)
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Assertion ID
|
BWS-TA-20004
|
|
Source
|
[BWS20004]
|
|
Target
|
The reference/binding.ws/@wsdlElement attribute
|
|
Prerequisites
|
The value of the attribute is of the form
<WSDL-namespace-URI>#wsdl.service(<service-name>)
|
|
Predicate
|
The set of available ports for that reference-binding is non-empty
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement” “reference target” “port”
|
|
Comment
|
Awkward wording. Plus the set of available ports is for the reference
binding not just the reference.
|
|
Assertion ID
|
BWS-TA-20005
|
|
Source
|
[BWS20005]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The value of the attribute reference/binding.ws/@wsdlElement is of the
form <WSDL-namespace-URI>#wsdl.service(<service-name>) and SCA
runtime does not support any of the available ports
|
|
Predicate
|
The SCA runtime raises an error
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement” “reference target” “error”
|
|
Assertion ID
|
BWS-TA-20006
|
|
Source
|
[BWS20006]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The value of the attribute reference/binding.ws/@wsdlElement is of the
form <WSDL-namespace-URI>#wsdl.service(<service-name>) and the
number of available ports is more than one
|
|
Predicate
|
The SCA runtime uses exactly one port for each invocation
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement” “reference target”
|
|
Comment
|
Untestable?
|
|
Assertion ID
|
BWS-TA-20007
|
|
Source
|
[BWS20007]
|
|
Target
|
The service/binding.ws/@wsdlElement attribute
|
|
Prerequisites
|
The value of the attribute is of the form
<WSDL-namespace-URI>#wsdl.port(<service-name>/<port-name>)
|
|
Predicate
|
The portType associated with the port is compatible with the service
interface and satisfies all the policy constraints of the binding
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Comment
|
Would require multiple tests
|
|
Assertion ID
|
BWS-TA-20008
|
|
Source
|
[BWS20008]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The value of the attribute service/binding.ws/@wsdlElement is of the
form
<WSDL-namespace-URI>#wsdl.port(<service-name>/<port-name>)
|
|
Predicate
|
The SCA runtime exposes the endpoint specified by the WSDL port or
raises an error if the port is not supported
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Assertion ID
|
BWS-TA-20009
|
|
Source
|
[BWS20009]
|
|
Target
|
The reference/binding.ws/@wsdlElement attribute
|
|
Prerequisites
|
The value of the attribute is of the form <WSDL-namespace-URI>#wsdl.port(<service-name>/<port-name>)
|
|
Predicate
|
The portType associated with the port is compatible superset of the
reference interface and satisfies all the policy constraints of the binding
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Comment
|
Would require multiple tests
|
|
Assertion ID
|
BWS-TA-20010
|
|
Source
|
[BWS20010]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The value of the attribute reference/binding.ws/@wsdlElement is of the
form
<WSDL-namespace-URI>#wsdl.port(<service-name>/<port-name>)
|
|
Predicate
|
The SCA runtime uses the endpoint specified by the WSDL port for
invocations or raises an error if the port is not supported
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Comment
|
Looks incorrect, what if there is an alternate binding specified?
|
|
Assertion ID
|
BWS-TA-20011
|
|
Source
|
[BWS20011]
|
|
Target
|
The service/binding.ws/@wsdlElement attribute
|
|
Prerequisites
|
The value of the attribute is of the form
<WSDL-namespace-URI>#wsdl.binding(<binding-name>)
|
|
Predicate
|
The portType associated with the WSDL binding is compatible with the
service interface and satisfies all the policy constraints of the binding
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Comment
|
Would require multiple tests
|
|
Assertion ID
|
BWS-TA-20012
|
|
Source
|
[BWS20012]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The value of the attribute service/binding.ws/@wsdlElement is of the
form <WSDL-namespace-URI>#wsdl.binding(<binding-name>)
|
|
Predicate
|
The SCA runtime exposes an endpoint using the specified WSDL binding or
raises an error if the WSDL binding is not supported
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Assertion ID
|
BWS-TA-20013
|
|
Source
|
[BWS20013]
|
|
Target
|
The reference/binding.ws/@wsdlElement attribute
|
|
Prerequisites
|
The value of the attribute is of the form <WSDL-namespace-URI>#wsdl.binding(<binding-name>)
|
|
Predicate
|
The portType associated with the WSDL binding is compatible superset of
the reference interface and satisfies all the policy constraints of the
binding
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Comment
|
Would require multiple tests
|
|
Assertion ID
|
BWS-TA-20014
|
|
Source
|
[BWS20014]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The value of the attribute reference/binding.ws/@wsdlElement is of the
form <WSDL-namespace-URI>#wsdl.binding(<binding-name>)
|
|
Predicate
|
The SCA runtime uses the WSDL binding specified for reference
invocations or raises an error if the WSDL binding is not supported
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Comment
|
Looks incorrect, what if there is an alternate binding specified?
|
|
Assertion ID
|
BWS-TA-20015
|
|
Source
|
[BWS20015]
|
|
Target
|
The reference/binding.ws/@wsdlElement attribute
|
|
Prerequisites
|
The value of the attribute is of the form
<WSDL-namespace-URI>#wsdl.binding(<binding-name>)
|
|
Predicate
|
The endpoint address is either specified by the reference/binding.ws/@uri
attribute, or the reference/binding.ws/EndpointReference element, except for
the cases where the SCA Assembly specification allows the @uri attribute to
be omitted
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement”
|
|
Comment
|
The predicate should be exampled to include the exception cases. Would
require multiple tests (positive and negative)
|
|
Assertion ID
|
BWS-TA-20016
|
|
Source
|
[BWS20017]
|
|
Target
|
The binding.ws element
|
|
Prerequisites
|
The attribute wsdli:wsdlLocation attribute is present
|
|
Predicate
|
The attribute wsdlElement is also present on the same binding.ws
element
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement” “wsdlLocation”
|
|
Assertion ID
|
BWS-TA-20017
|
|
Source
|
[BWS20018]
|
|
Target
|
The binding.ws/@wsdli:wsdlLocation attribute
|
|
Prerequisites
|
|
|
Predicate
|
The attribute value points to an existing WSDL 1.1 document
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlLocation”
|
|
Comment
|
Minor quibble: why is
'existing' needed here?
Also it should say something more: it shouldn't just point to any WSDL
1.1 doc, but a doc that contain artifacts related to the element pointed to
by the wsdlElement attr
|
|
Assertion ID
|
BWS-TA-20018
|
|
Source
|
[BWS20019]
|
|
Target
|
The binding.ws element
|
|
Prerequisites
|
|
|
Predicate
|
The uri attribute, the endpointReference element and the wsdlElement
attribute referring to a WSDL port or service are mutually exclusive
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement” “uri” “endpoint reference”
|
|
Assertion ID
|
BWS-TA-20019
|
|
Source
|
[BWS20020]
|
|
Target
|
The service/callback/binding.ws element
|
|
Prerequisites
|
|
|
Predicate
|
The uri attribute or endpointReference element are absent
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“callback” “uri” “endpoint reference”
|
|
Assertion ID
|
BWS-TA-20020
|
|
Source
|
[BWS20021]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
|
|
Predicate
|
All attributes of binding.ws, i.e., name, uri, requires, policSets,
wsdlElement, wsdli:wsdlLocation are supported
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“wsdlElement” “uri” “requires” “policySets” “name” “wsdlLocation”
|
|
Assertion ID
|
BWS-TA-20021
|
|
Source
|
[BWS20022]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
|
|
Predicate
|
binding.ws/endpointReference element is supported
|
|
Prescription Level
|
Preferred
|
|
Tags
|
“endpointReference” “SCA runtime”
|
|
Assertion ID
|
BWS-TA-20022
|
|
Source
|
[BWS20023]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
SCA runtime does not support binding.ws/endpointReference element
|
|
Predicate
|
Rejects any conformant SCA WS Binding XML document that contains
binding.ws/endpointReference element
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“endpointReference” “SCA runtime”
|
|
Assertion ID
|
BWS-TA-20023
|
|
Source
|
[BWS20024]
|
|
Target
|
binding.ws element
|
|
Prerequisites
|
|
|
Predicate
|
Conforms to the schema defined in sca-binding-webservice-1.1.xsd
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“schema”
|
|
Assertion ID
|
BWS-TA-20024
|
|
Source
|
[BWS20025]
|
|
Target
|
<binding.ws/> subelement of a component <reference> element
|
|
Prerequisites
|
binding.ws does not contain a target address
|
|
Predicate
|
SCA runtime raises an error
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“target address” ”SCA runtime”
|
|
Assertion ID
|
BWS-TA-20025
|
|
Source
|
[BWS20026]
|
|
Target
|
<binding.ws/> subelemement of a component <reference/>
|
|
Prerequisites
|
The binding.ws element has a valid target specified by one of the
mechanisms defined in the specification section "Endpoint URI
resolution"
|
|
Predicate
|
The target address is used by the runtime when the component
implementation invokes an operation of the reference
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“target address”
|
|
Assertion ID
|
BWS-TA-20026
|
|
Source
|
[BWS20027]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
binding.ws is used on a service or a reference that has an interface
which is not defined using interface.wsdl
|
|
Predicate
|
A WSDL portType is derived for the service or the reference using the
mapping rules defined for that interface type
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“sca runtime” “interface mapping”
|
|
Comment
|
s/rules/WSDL-mapping rules/
|
|
Assertion ID
|
BWS-TA-20027
|
|
Source
|
[BWS20028]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
binding.ws is used on a service or a reference that has an interface
which is not defined using interface.wsdl
|
|
Predicate
|
An error is raised if the interface used cannot be mapped to a WSDL
portType
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“sca runtime” “interface mapping”
|
|
Assertion ID
|
BWS-TA-20028
|
|
Source
|
[BWS20029]
|
|
Target
|
A service that uses binding.ws with an HTTP endpoint is hosted by the
SCA runtime
|
|
Prerequisites
|
|
|
Predicate
|
The service returns a WSDL description of itself in response to an HTTP
GET request with the “?wsdl” suffix added to the service endpoint URL
|
|
Prescription Level
|
Preferred
|
|
Tags
|
“sca runtime” “HTTP GET” “WSDL description”
|
|
Comment
|
|
|
Assertion ID
|
BWS-TA-20029
|
|
Source
|
[BWS20030]
|
|
Target
|
A service that uses one of more instances of binding.ws but none of
them have HTTP endpoints
|
|
Prerequisites
|
|
|
Predicate
|
The SCA runtime provides some means for obtaining the WSDL description
of the service
|
|
Prescription Level
|
Preferred
|
|
Tags
|
“sca runtime” “WSDL description”
|
|
Assertion ID
|
BWS-TA-20030
|
|
Source
|
[BWS20032]
|
|
Target
|
<binding.ws/> element which references a WSDL document by means
of its @wsdlElement attribute
|
|
Prerequisites
|
The referenced WSDL document contains one or more of the extensions
defined in the SCA namespace "http://docs.oasis-open.org/ns/opencsa/sca/200912" as
defined in the SCA Assembly specification
|
|
Predicate
|
The SCA runtime supports the SCA WSDL extensions contained in the WSDL document
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“sca runtime” “WSDL extension”
|
|
Assertion ID
|
BWS-TA-20031
|
|
Source
|
[BWS20033]
|
|
Target
|
<binding.ws/> element which references a Binding in a WSDL
document by means of its @wsdlElement attribute
|
|
Prerequisites
|
The WSDL Binding element uses the SOAP 1.1 over HTTP binding, using a
wsoap11:binding that has the @transport attribute with a value of
"http://schemas.xmlsoap.org/soap/http"
|
|
Predicate
|
The binding.ws element is supported by the SCA runtime and it is
possible to invoke a service operation successfully through the reference or
service which uses the binding.ws element.
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“sca runtime” “WSDL extension” “SOAP 1.1”
|
|
Assertion ID
|
BWS-TA-20032
|
|
Source
|
[BWS20034]
|
|
Target
|
<binding.ws/> element which references a Binding in a WSDL
document by means of its @wsdlElement attribute
|
|
Prerequisites
|
The WSDL Binding element uses the SOAP 1.2 over HTTP binding, using a
wsoap12:binding that has the @transport attribute with a value of
"http://schemas.xmlsoap.org/soap/http"
|
|
Predicate
|
The binding.ws element is supported by the SCA runtime and it is
possible to invoke a service operation successfully through the reference or
service which uses the binding.ws element.
|
|
Prescription Level
|
Preferred
|
|
Tags
|
“sca runtime” “WSDL extension” “SOAP 1.2”
|
|
Assertion ID
|
BWS-TA-20033
|
|
Source
|
[BWS20035]
|
|
Target
|
<bindingType> element associated with binding.ws
|
|
Prerequisites
|
|
|
Predicate
|
The <bindingType> element associated with binding.ws includes the
SOAP.v1_1 intent in its @mayProvides or @alwaysProvides attributes
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SOAP 1.1” “bindingType” “intent” “mayProvides” “alwaysProvides”
|
|
Comment
|
|
|
Assertion ID
|
BWS-TA-20034
|
|
Source
|
[BWS20036]
|
|
Target
|
<bindingType> element associated with binding.ws
|
|
Prerequisites
|
|
|
Predicate
|
The <bindingType> element associated with binding.ws includes the
SOAP.v1_2 intent in its @mayProvides attribute
|
|
Prescription Level
|
Preferred
|
|
Tags
|
“SOAP 1.2” “bindingType” “intent” “mayProvides”
|
|
Comment
|
|
|
Assertion ID
|
BWS-TA-20035
|
|
Source
|
[BWS20037]
|
|
Target
|
<binding.ws/> element configured with a policy intent
|
|
Prerequisites
|
The policy intent conflicts with the configuration of the
<binding.ws/> element
|
|
Predicate
|
SCA runtime raises an error
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “intent”
|
2.2 Section 4 Test Assertions
|
Assertion ID
|
BWS-TA-40001
|
|
Source
|
[BWS40001]
|
|
Target
|
Component <service/> or <reference/> with a
<binding.ws/> subelement
|
|
Prerequisites
|
SOAP intent is applied to the <binding.ws/> element
|
|
Predicate
|
The <service/> or <reference/> transmits and receives
messages using one or more versions of SOAP
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “intent” “SOAP”
|
|
Assertion ID
|
BWS-TA-40002
|
|
Source
|
[BWS40002]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
SOAP.v1_1 intent is required
|
|
Predicate
|
The SCA runtime transmits and receives messages using only SOAP 1.1
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “intent” “SOAP”
|
|
Assertion ID
|
BWS-TA-40003
|
|
Source
|
[BWS40003]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
SOAP.v1_2 intent is required
|
|
Predicate
|
The SCA runtime transmits and receives messages using only SOAP 1.2
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “intent” “SOAP”
|
|
Assertion ID
|
BWS-TA-40004
|
|
Source
|
[BWS40004]
|
|
Target
|
portType of an SCA component <service/> or <reference/>
element
|
|
Prerequisites
|
portType is either explicitly specified or is derived from the
interface specified for the service or reference
|
|
Predicate
|
The portType follows either the rpc-literal pattern or
the document-literal pattern
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “intent” “SOAP”
|
|
Comment
|
|
|
Assertion ID
|
BWS-TA-40005
|
|
Source
|
[BWS40005]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The transport details are not otherwise determined
|
|
Predicate
|
The default transport binding rules are used
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “default transport binding rules”
|
|
Comment
|
The precondition is vague. What does 'not otherwise determined' mean?
Shouldn't we enumerate when this happens?
|
|
Assertion ID
|
BWS-TA-40007
|
|
Source
|
[BWS40007]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
Default transport binding rules are used along with rpc-literal pattern
|
|
Predicate
|
SCA runtime uses the structural URI associated with the binding as the
namespace of the child elements of the SOAP body element
|
|
Prescription Level
|
Preferred
|
|
Tags
|
“SCA runtime” “default transport binding rules” “rpc-literal”
|
2.3 Section 5 Test Assertions
|
Assertion ID
|
BWS-TA-50001
|
|
Source
|
[BWS50002]
|
|
Target
|
Web service request message sent to a Web service endpoint
|
|
Prerequisites
|
a) Web service endpoint has
an interface with an associated callback (ie. it is bidirectional)
b) SCA Web Services Callback Protocol is used
|
|
Predicate
|
Request message contains a Callback EPR, either in the wsa:From SOAP
header block or in the wsa:ReplyTo SOAP header block
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “SCA Web Services Callback Protocol”
|
|
Assertion ID
|
BWS-TA-50002
|
|
Source
|
[BWS50004]
|
|
Target
|
SCA bidirectional service using
the binding.ws binding with the SCA Web Services Callback Protocol
|
|
Prerequisites
|
The service receives an operation invocation of the service where the
Callback EPR's address value is
"http://www.w3.org/2005/08/addressing/anonymous" or
"http://www.w3.org/2005/08/addressing/none"
|
|
Predicate
|
An Invalid Addressing Header fault is generated as specified in Section
6.4.1 of WS-Addressing 1.0 SOAP Binding
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “SCA Web Services Callback Protocol” “callback EPR”
|
|
Assertion ID
|
BWS-TA-50003
|
|
Source
|
[BWS50005]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The callback interface is invoked using the SCA Web Services Callback
Protocol
|
|
Predicate
|
The Callback EPR from a request message that invoked the forward
interface is used to invoke the callback interface
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “SCA Web Services Callback Protocol” “callback EPR”
|
|
Assertion ID
|
BWS-TA-50004
|
|
Source
|
[BWS50006]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The Callback EPR is selected to invoke the callback interface
|
|
Predicate
|
The rules defined in Section 3.3 of WS-Addressing 1.0 – Core are followed
to invoke operations on the callback interface using the Callback EPR
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “SCA Web Services Callback Protocol” “callback EPR”
|
|
Assertion ID
|
BWS-TA-50005
|
|
Source
|
[BWS50007]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The request message from which the Callback EPR was obtained contained
the wsa:MessageID SOAP header block
|
|
Predicate
|
The callback message contains the wsa:RelatesTo SOAP header block
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “SCA Web Services Callback Protocol” “callback EPR”
|
|
Assertion ID
|
BWS-TA-50006
|
|
Source
|
[BWS50008]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The request message from which the Callback EPR was obtained contained
the wsa:MessageID SOAP header block
|
|
Predicate
|
The wsa:RelatesTo SOAP header block in the callback message has the
relationship type value of
"http://docs.oasis-open.org/opencsa/sca-bindings/ws/callback" and
the related message id is the wsa:MessageID of the message from which the
Callback EPR was obtained
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “SCA Web Services Callback Protocol” “callback EPR”
|
|
Assertion ID
|
BWS-TA-50007
|
|
Source
|
[BWS50009]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
The request message from which the Callback EPR was obtained does not
contain the wsa:MessageID SOAP header block
|
|
Predicate
|
The callback message does not contain the wsa:RelatesTo SOAP header
block with a relationship type value of
"http://docs.oasis-open.org/opencsa/sca-bindings/ws/callback"
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “SCA Web Services Callback Protocol” “callback EPR”
|
|
Assertion ID
|
BWS-TA-50008
|
|
Source
|
[BWS50010]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
WSCallback policy assertion is present in the effective policy of a
service/binding or a reference/binding
|
|
Predicate
|
The SCA Web Services Callback Protocol is used to invoke callbacks for
that binding
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“SCA runtime” “SCA Web Services Callback Protocol” “WSCallback policy
assertion”
|
|
Assertion ID
|
BWS-TA-50009
|
|
Source
|
[BWS50013]
|
|
Target
|
WSDL document (?)
|
|
Prerequisites
|
|
|
Predicate
|
The wsdl:portType that is used does not have WSCallback policy
assertion attached
|
|
Prescription Level
|
Mandatory
|
|
Tags
|
“WSCallback policy assertion”
|
|
Comment
|
We haven't defined WSDL document as the target. Is the appropriate
target the composite/CT document that points to such a WSDL?
|
|
Assertion ID
|
BWS-TA-50010
|
|
Source
|
[BWS50014]
|
|
Target
|
?
|
|
Prerequisites
|
Policy contains WSCallback policy assertion
|
|
Predicate
|
The policy or the assertion is signed
|
|
Prescription Level
|
Preferred
|
|
Tags
|
“WSCallback policy assertion”
|
|
Comment
|
Policies can be inlined or attached. Which target should be used: WSDL
doc, policy attachments, composites/CT/impl code, all of them?
|
|
Assertion ID
|
BWS-TA-50011
|
|
Source
|
[BWS50015]
|
|
Target
|
SCA runtime
|
|
Prerequisites
|
Policy contains WSCallback policy assertion which is either not signed
or does not have an associated security token to specify that the signer has
the proper claims for the policy
|
|
Predicate
|
The policy is rejected
|
|
Prescription Level
|
Preferred
|
|
Tags
|
“WSCallback policy assertion”
|
3 Cross Mapping of Conformance Statements to Assertions
|
Conformance statement
|
Test Assertion
|
|
BWS20001
|
BWS-TA-20001
|
|
BWS20002
|
BWS-TA-20002
|
|
BWS20003
|
BWS-TA-20003
|
|
BWS20004
|
BWS-TA-20004
|
|
BWS20005
|
BWS-TA-20005
|
|
BWS20006
|
BWS-TA-20006
|
|
BWS20007
|
BWS-TA-20007
|
|
BWS20008
|
BWS-TA-20008
|
|
BWS20009
|
BWS-TA-20009
|
|
BWS20010
|
BWS-TA-20010
|
|
BWS20011
|
BWS-TA-20011
|
|
BWS20012
|
BWS-TA-20012
|
|
BWS20013
|
BWS-TA-20013
|
|
BWS20014
|
BWS-TA-20014
|
|
BWS20015
|
BWS-TA-20015
|
|
BWS20017
|
BWS-TA-20016
|
|
BWS20018
|
BWS-TA-20017
|
|
BWS20019
|
BWS-TA-20018
|
|
BWS20020
|
BWS-TA-20019
|
|
BWS20021
|
BWS-TA-20020
|
|
BWS20022
|
BWS-TA-20021
|
|
BWS20023
|
BWS-TA-20022
|
|
BWS20024
|
BWS-TA-20023
|
|
BWS20025
|
BWS-TA-20024
|
|
BWS20026
|
BWS-TA-20025
|
|
BWS20027
|
BWS-TA-20026
|
|
BWS20028
|
BWS-TA-20027
|
|
BWS20029
|
BWS-TA-20028
|
|
BWS20030
|
BWS-TA-20029
|
|
BWS20032
|
BWS-TA-20030
|
|
BWS20033
|
BWS-TA-20031
|
|
BWS20034
|
BWS-TA-20032
|
|
BWS20035
|
BWS-TA-20033
|
|
BWS20036
|
BWS-TA-20034
|
|
BWS20037
|
BWS-TA-20035
|
|
Conformance statement
|
Test Assertion
|
|
BWS40001
|
BWS-TA-40001
|
|
BWS40002
|
BWS-TA-40002
|
|
BWS40003
|
BWS-TA-40003
|
|
BWS40004
|
BWS-TA-40004
|
|
BWS40005
|
BWS-TA-40005
|
|
BWS40007
|
BWS-TA-40007
|
|
Conformance statement
|
Test Assertion
|
|
BWS50002
|
BWS-TA-50001
|
|
BWS50004
|
BWS-TA-50002
|
|
BWS50005
|
BWS-TA-50003
|
|
BWS50006
|
BWS-TA-50004
|
|
BWS50007
|
BWS-TA-50005
|
|
BWS50008
|
BWS-TA-50006
|
|
BWS50009
|
BWS-TA-50007
|
|
BWS50010
|
BWS-TA-50008
|
|
BWS50013
|
BWS-TA-50009
|
|
BWS50014
|
BWS-TA-50010
|
|
BWS50015
|
BWS-TA-50011
|
There are no conformance statements relating to the Test
Assertions.
The following individuals have participated in the creation
of this specification and are gratefully acknowledged
Participants:
·
Mike Edwards, IBM
·
Anish Karmarkar, Oracle
Appendix B.
Revision History
|
Revision
|
Date
|
Editor
|
Changes Made
|
|
wd01
|
09/09/09
|
Anish Karmarkar
|
Created the initial draft with the first 15 assertions
|
|
wd02
|
07/10/09
|
Anish Karmarkar
|
Included all the assertions and mappings
|
|
wd03
|
22/03/10
|
Anish Karmarkar
|
Synched up with cd03-rev2 + misc ed changes
|
|
wd04
|
07/06/10
|
Mike Edwards
|
Updated text for TAs:
20023, 20024, 20025, 20028, 20029, 20030, 20031, 20032, 20033, 20034,
20035, 40001, 40004, 50001, 50002
|
|
wd05
|
14/06/10
|
Mike Edwards
|
Formatting corrections
|
|
cd01
|
01/07/10
|
Mike Edwards
|
All changes accepted
Frontmatter corrected to OASIS requirements
|