Here's what I see for assembly/javacaa/javaci...
I have closed TUSCANY-3480 and reverted the change as this is not the
immediate root cause of the remaining problems.
Assembly
testDummy(client.ASM_6015_TestCase) - There is an assumption in the
test case that binding.sca "mayProvide"
confidentilaity and integrity.
However there is currently no requirement
in the spec that this is the
case as far as I can tell.
Action: get confirmation from OASIS
if yes fix our binding.sca
if no OASIS to fix the test
Java CAA
testDummy(client_javacaa.JCA_8005_TestCase)
SEVERE: = Unable to match the endpoint reference
(@1135890)EndpointReference: URI =
TEST_JCA_8005Component1#reference(reference2) WIRED_TARGET_NOT_FOUND
Target = (@31992690)Endpoint: URI = TEST_JCA_8005Component3
[Unresolved] with the policy of the service to which it refers,
matching process was Match policy of (@1135890)EndpointReference: URI
= TEST_JCA_8005Component1#reference(reference2) WIRED_TARGET_NOT_FOUND
Target = (@31992690)Endpoint: URI = TEST_JCA_8005Component3
[Unresolved] to (@28138822)Endpoint: URI =
TEST_JCA_8005Component3#service-binding(Service1/Service1) No match
because there are unresolved intents
[{http://docs.oasis-open.org/ns/opencsa/scatests/200903}testIntent2]
CAA doesn't define a policy set for this intent. Only provides
policy sets to intents 3 and 5 (possibly on purpose)
Now it may very well be a builder problem not getting the right
intents at the service but it's not a matching problem
testDummy(client_javacaa.JCA_8007_TestCase)
SEVERE: = Unable to match the endpoint reference
(@19896612)EndpointReference: URI =
TEST_JCA_8007Component1#reference(reference1) WIRED_TARGET_NOT_FOUND
Target = (@32453138)Endpoint: URI = TEST_JCA_8007Component2
[Unresolved] with the policy of the service to which it refers,
matching process was Match policy of (@19896612)EndpointReference:
URI = TEST_JCA_8007Component1#reference(reference1)
WIRED_TARGET_NOT_FOUND Target = (@32453138)Endpoint: URI =
TEST_JCA_8007Component2 [Unresolved] to (@12612903)Endpoint: URI =
TEST_JCA_8007Component2#service-binding(Service5Intents/Service5Intents)
No match because there are unresolved intents
[{http://docs.oasis-open.org/ns/opencsa/scatests/200903}testIntent4]
CAA doesn't define a policy set for this intent. Only provides
policy sets to intents 3 and 5 (possibly on purpose)
Now it may very well be a builder problem not getting the right
intents at the service but it's not a matching problem
Java CI
testDummy(client_javapojo.POJO_8003_TestCase)
SEVERE: Intent
{http://docs.oasis-open.org/ns/opencsa/sca/200903}propagatesTransaction
is not defined in SCA definitions
Incorrect namespace for intent in
org.oasisopen.sca.test.service1WithIntentImpl
Looks like somehow an incorrect version of the SCA API module is
being pulled in
testDummy(client_javapojo.POJO_8012_TestCase)
SEVERE: Intent
{http://docs.oasis-open.org/ns/opencsa/sca/200903}managedTransaction
is not defined in SCA definitions
Incorrect namespace for intent in
org.oasisopen.sca.test.service1WithIntentImpl
Looks like somehow an incorrect version of the SCA API module is
being pulled in
I'll create JIRA for these issues where they don't exist.
I would like to ensure that the tests that fail for issues that we are
in conversation with OASIS for continue
to fail explicitly. In this way when OASIS TC members run the tests
using Tuscany the issues are obvious to them.
As I've said before I'd also like to see us fix any problems that
appear to require Tuscany runtime fixes rather than working around
them and giving the false impression that we are passing more tests
than we really are.
I'll review the policy tests shortly.
Regards
Simon
