On Mon, Apr 12, 2010 at 3:18 PM, Simon Laws <[email protected]> wrote:
> Still getting oom with JCAA so looking at that. Also I've had to
> locally fix a schema validation error in the JCAA tests. Do we have
> local changes in the OASIS assets we are using to run the compliance
> tests? If so is there a list somewhere?
>
> Simon
>
The local mod i have on the JCAA tests which is also what the
contributions used by the trunk compliance tests is:
Index: JCA_General_POJO/src/main/resources/TestClient_0002.composite
===================================================================
--- JCA_General_POJO/src/main/resources/TestClient_0002.composite
(revision 133)
+++ JCA_General_POJO/src/main/resources/TestClient_0002.composite
(working copy)
@@ -29,7 +29,7 @@
<property name="testName" source="$testName"/>
</component>
- <reference name="reference1"
promote="TestClient_0002TestClient/reference1">
+ <reference name="reference1" multiplicity="1..1"
promote="TestClient_0002TestClient/reference1">
<interface.java interface="org.oasisopen.sca.test.Service1"/>
</reference>
Index: JCA_General_POJO/src/main/resources/META-INF/definitions.xml
===================================================================
--- JCA_General_POJO/src/main/resources/META-INF/definitions.xml
(revision 133)
+++ JCA_General_POJO/src/main/resources/META-INF/definitions.xml
(working copy)
@@ -38,4 +38,8 @@
</policySet>
+ <policySet name="PolicySet4" provides="test:testIntent4"
appliesTo="//binding.ws">
+ <!-- This policy intentionally left blank -->
+ </policySet>
+
</definitions>
...ant