From: Mike Edwards
[mailto:mike_edwards@uk.ibm.com]
Sent: 23 February 2010 15:09
To: OASIS Assembly
Subject: [sca-assembly] [ASSEMBLY 205] TEST_ASM_12001 has empty
composite name - Propose CNA
Folks,
Assembly issue
205 (http://www.osoa.org/jira/browse/ASSEMBLY-205
) argues that
testcase
ASM_12001 is invalid since the TestConfiguration contains a set of
Contributions to use, but
does not supply
the name of any Composite to run.
My view is that
the testcase is valid and does not need to be changed. Hence we should
close this issue with no action.
Here is the
configuration in the test client:
config.testName
= this.getClass().getSimpleName().substring(0,
9);
config.input
= "request";
config.output[0]
=
config.testName + "
" + config.input + " service1 operation1 invoked" ;
// null composite supplied -
the name of the composite to run comes from the sca-contribution.xml
config.composite
= null;
config.testServiceName
= "TestClient";
config.contributionNames
= new
String[] { "ASM_12001", "General", "General"
+ _Lang };
The relevant
things are:
a) the list of
contribution names assigned to config.contributionNames
b) the value of
config.composite, which is null
In the design
of all the testcases, the configuration has one or more Contributions, which
are intended to contain the artifacts to use, plus
the name of a
Composite to run. It is expected that the Composite exists somewhere in
the supplied Contributions.
In this
testcase, one of the contributions - ASM_12001 - has an SCA contribution which
has a contribution.xml file as follows:
<contribution
xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912"
xmlns:test="http://docs.oasis-open.org/ns/opencsa/scatests/200903">
<deployable
composite="test:TEST_ASM_12001"/>
<import
namespace="http://docs.oasis-open.org/ns/opencsa/scatests/200903"/> <!-- Contributions namespace -->
<import
namespace="http://test.sca.oasisopen.org/"/>
<!-- WSDL namespace -->
</contribution>
Note the
presence of the <deployable/> element, referencing a specific Composite.
The design of
this test is intended to check that the SCA runtime will deploy the composite
referenced by the <deployable/> element.
Either this
test is correct as written, or the argument must be made that an SCA runtime
does not have to do anything with the <deployable/> element.
If that is the
case, then the whole testcase should be removed as the function is optional.
Yours, Mike.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email: mike_edwards@uk.ibm.com
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