[Issue 227] SCA-J POJO Component Implementation v1.1 TestCases Version1.0

Thanks for your comments.
This is filed as issue JAVA-227 [1] and will be considered by the SCA-J 
TC on one of their future calls after the holiday break.

-Anish
--

[1] http://osoa.org/jira/browse/JAVA-227


On 12/23/2010 6:20 PM, Patrick Durusau wrote:
> Greetings!
>
> Comments on behalf of the TAB.
>
> General comment: It was unclear where the Java classes could be found
> that are used in the test assertions. Seems like that would be fairly
> critical to the test cases. Yes?
>
> Test Artifact Organization
>
> read (in part):
>
>> Note that the design of these testcases promotes reuse of artifacts
>> between testcases, so that many testcases share components. For
>> example, components implementing simple invokable services are all
>> implemented using a single parameterized implementation artifact.
>> All the test artifacts are contained in a number of Contributions,
>> which are simply filesystem directories which are all peers in the
>> filesystem hierarchy. The names of the directories are the names of
>> the Contributions and the names are significant. The names of
>> Contributions containing implementation type specific artifacts (such
>> as Java classes) are also specially structured to allow for
>> replacement of one type of implementation artifact with another.
>
> Really should have a clear separation between normative and
> non-normative material. Such as starts with "Note that..." is
> non-normative.
>
> In the absence of the Java classes or specification of the purpose of
> those classes, it isn't possible to evaluate the various test cases.
>
> 5 Conformance
>
> No conformance clauses? Contrary to OASIS policy.
>
> Hope everyone is having a great holiday season!
>
> Patrick
>