OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-assembly] Fabric3 Fulfillment of Assembly TC Exit Criteria


I have raised some process questions on the Java TC mailing list about the potential timing of being able to accepting any Spring implementation as conforming at the current time. But there is also a question that this TC needs to consider regarding our exit criteria.

Provided the Java TC accepts the Fabric conformance submission, there would be one conforming implementation of the POJO CI spec (Tuscany) and one conforming implantation of the Spring CI spec (Fabric3). Does this fulfill the exit criteria for the Assembly spec? A case could certainly be made, but I would like to know what others think.

Bryan Aupperle. PhD
Executive Software Client Architect - Mid-Atlantic
Senior Technical Staff Member


Raleigh, NC
Mobile: 919-656-0018
aupperle@us.ibm.com




From:        Jim Marino <jim.marino@gmail.com>
To:        sca-assembly@lists.oasis-open.org,
Date:        03/09/2013 01:35 AM
Subject:        [sca-assembly] Fabric3 Fulfillment of Assembly TC Exit Criteria
Sent by:        <sca-assembly@lists.oasis-open.org>




All,

This message is intended to provide notice that Fabric3 meets the conformance and Exit Criteria requirements as defined by the Assembly Specification v.1.1 in Section 12.2 and the Assembly TC Charter respectively. 

Specifically:

1. Fabric3 conforms to all mandatory and optional normative statements as defined by

a. The Assembly Specification, Section C. Proof of passing the TC Assembly Test Suite, including runtime source code, was submitted and accepted via resolution as detailed here:  http://bit.ly/WMl9M4.

b. The SCA Policy Framework Specification v1.1, including all normative statements for direct and external attachment. Proof of passing the TC Policy Test Suite, including runtime source code, was submitted to the TC mailing list on March 6, 2013. 

c. The Spring Component Implementation Specification v1.1. Proof of passing the TC Spring Test Suite, including runtime source code, was submitted to the TC mailing list on March 9, 2013.

d. The Web Services Binding Specification v1.1. Proof of passing the TC WS Binding Test Suite, including runtime source code, was submitted to the TC mailing list on March 3, 2013. 

Along with Apache Tuscany conformance, I believe this evidence of Fabric3 conformance fulfills the TC Exit criteria. Namely, that there shall be at least two independent runtimes which are compliant with all normative portions of the specifications in question and demonstrate interoperability and portability as appropriate. 

Jim



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]