>> > > AFAICT these tests aren't working correctly yet and the otests are > just passing because they only check for a ServiceRuntimeException and > not checking for any message about what the test is testing, thats in > both the otests and trunk. > > ...ant >
I'm seeing the same Ant. While the tests are passing for me the reason that they're passing is that the expected error messages are not included in the tuscany-oasis-sca-tests-errors.properties files. A generic message is being produced instead. Having said that I don't understand how these tests will work. I think the initial assumption was that some of the implementation and binding type extensions would "provide" transactional policies by default. We may need to do this to accommodate the extension specific nature of the policies. However, at the moment we only have the explicit policy set part of the transaction policies. In the context of the change I posted about (but haven't committed yet) where the runtime will no longer automatically attach policy sets based on intent configuration we are unable to attach the transaction policy sets to the 900X otest composites and so I imagine the tests will always fail with "intent not satisfied" rather than whatever error they are supposed to fail with. I think we need to take guidance from the OASIS team regarding how they are going to (re-)construct these tests in the context of the policy spec as it stands at the moment. Simon
