Re: [sca-j] Fabric3 declaration of SCA 1.1 Spring Component Implementation Specification conformance and fulfillment of the TC Exit Criteria requirements

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

On 03/25/2013 10:39 AM, Bryan Aupperle wrote:
> I have several questions of a status/process nature.
>
> 1) I cannot find a CSD level document for the Spring test cases, only a
> working draft. Can anyone point to a CSD or even better a PRD?

http://docs.oasis-open.org/opencsa/sca-j/sca-springci-spec/v1.1/sca-springci-spec-v1.1.pdf

You probably didn't find it because we decided to move to subdirectories 
for various specs (instead of having all the specs in one directory) 
just before we published Spring CI.

BTW, we never published a CSD or PR for the test assertions or test cases.

> 2) If there has not been a public review of these test cases, can we
> reasonably accept any implementation as conforming at this time?

There has been a PR for CSD01

> 3) This Spring CI spec conformance section does not explicitly require
> that an implementation conform to the Java CAA spec. Is this an
> oversight? Consider this in light of: "The introspected component type
> MUST be a compliant SCA Java XML Document as defined in section 12.1 of
> [JAVA-CAA]. [SPR30003]" which implies this requirement.

Probably and oversight.
Given the other MUST statements in the document, I would assert that 
conformance to CAA (at least to those things that affect the interface 
and CT) are required.


> 4) If we accept this, we would have one conforming implementation of the
> Java CAA spec (Tuscany), 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 any of the specs? I
> do not believe so but would like to know what others think.

I don't believe so either.

> 5) If Fabric3 submits acceptable proof of conformance to the Java CAA
> spec, is that sufficient for two conforming Java implementations or is
> that up to the Assembly TC to decide?

I'll respond to this on the assembly thread that you have created.

-Anish
--

> 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-j@lists.oasis-open.org,
> Date: 03/09/2013 12:54 AM
> Subject: [sca-j] Fabric3 declaration of SCA 1.1 Spring Component
> Implementation Specification conformance and fulfillment of the TC Exit
> Criteria requirements
> Sent by: <sca-j@lists.oasis-open.org>
> ------------------------------------------------------------------------
>
>
>
> All,
>
> Attached please find output from the OASIS SCA 1.1 Spring Component
> Implementation Test Suite successfully run against the Fabric3 runtime.
> This output demonstrates that Fabric3 conforms to all normative
> statements of the SCA 1.1 Spring Component Implementation Specification.
>
> The Test Suite adaptation to integrate and verify the Fabric3 runtime
> can be found here:
>
> _https://github.com/Metaform/fabric3-conformance-spring_
>
> Note that the README file contains instructions for building the runtime
> and executing the Test Suite, which requires JDK 6 and Maven 3.0.4.
>
> I believe these results fulfill the SCA 1.1 Spring Component
> Implementation Exit Criteria requirements as laid out in the TC charter.
>
> Regards,
> Jim
>
> [attachment "spring.conformance.output.txt" deleted by Bryan
> Aupperle/Raleigh/IBM]
> ---------------------------------------------------------------------
> 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