[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Evidence for an SCA Runtime which Conforms with the SCA JMS BindingSpecification Version 1.1 and meets the requirements of the Exit Criteria
I present evidence for an SCA Runtime which Conforms to the SCA JMS Binding
Specification Version 1.1 and meets the requirements of the Exit Criteria.
I would like this considered by the TC at its next meeting.
The SCA Runtime is Apache Tuscany SCA Java Implementation Project (2.x) at
the 2.0-SNAPSHOT level, Revision 1166718.
The runtime can be accessed in source and binary format here:
http://tuscany.apache.org/
As evidence that this SCA Runtime does conform to the SCA JMS Binding
Specification Version 1.1, here I present a report of the output of
executing the OASIS SCA JMS Binding V1.1 Test Suite (Revision 310) against
this runtime, performed using the Maven tooling:
(See attached file: surefire-report.pdf)
...ant
Simon
Holdsworth/UK/IBM
@IBMGB To
sca-bindings@lists.oasis-open.org
24/08/2011 13:59 cc
Subject
[sca-bindings] Call for Web Service
and JMS Binding Implementations
Folks,
In the last SCA Bindings TC meeting [1] we defined the exit criteria for
the Web Service and JMS Binding specifications, copied below for your
convenience. To that end, I would appreciate it if members of the TC could
bring forward any suitable Web Service and JMS binding implementations
along with evidence to show compliance with the exit criteria, so that the
specifications are able to progress through the standardisation process.
The Concrete Exit Criteria for the SCA Web Service Binding V1.1
specification are that:
1) there shall be at least 2 independent SCA runtimes each of which are
compliant with all normative portions of the specification that apply to
SCA runtimes as described in Section 6.4 of the SCA Web Service Binding
V1.1 specification, and
2) there shall be at least 2 independent runtimes each of which are
compliant with all normative portions of the specification that apply to a
Web Service Callback Service as described in Section 6.2 of the SCA Web
Service Binding V1.1 specification, and
3) there shall be at least 2 independent runtimes each of which are
compliant with all normative portions of the specification that apply to a
Web Service Callback Client as described in Section 6.3 of the SCA Web
Service Binding V1.1 specification.
4) Each implementation should provide evidence of interop/portability, as
appropriate. Output from the Web Service Binding V1.1 testsuite is
considered sufficient evidence
The Concrete Exit Criteria for the SCA JMS Binding V1.1 specification are
that:
1) there shall be at least 2 independent SCA runtimes each of which are
compliant with all normative portions of the specification as described in
Section 8.2 of the SCA JMS Binding V1.1 specification.
2) Each implementation should provide evidence of interop/portability, as
appropriate. Output from the JMS Binding V1.1 testsuite is considered
sufficient evidence
[1]
http://www.oasis-open.org/committees/download.php/43271/SCA%20Bindings%20minutes%202011-08-18.doc
Thanks, Simon
SCA Bindings TC Chair
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]