The Assembly and Java CAA tests are all passing and all but three of the POJO (Java CI) one, so that leaves remaining:
- The Java component type calculation with @Requires to fix the three Java CI fails - TUSCANY-3480 - The policy test failures which are these (with a bit of text added to say what the test is about): POL_3001 intent conflicts with binding (requires SOAP but wsdl has EJB binding) POL_3002 policyset conflicts with binding (requires SOAP but wsdl has EJB binding) POL_3003 definitions.xml with duplicat intents POL_4003 externally attached policy sets POL_4012 mutually exclusive intents POL_4027 duplicate bindingType definitions POL_4028 policySet/@attachTo points to a property POL_5001 unknown implementation types POL_9006 reference with transactedOneWay on a non-global tran component POL_9009 service with transactedOneWay on a non-global tran component POL_9015 managedTransaction.local and a service with propagatesTransaction POL_9016 noManagedTransaction and a service with propagatesTransaction POL_9017 reference with propagatesTransaction on a local tran component POL_9018 reference with propagatesTransaction on a noManagedTransaction component POL_10001 noListener intent is not used on a service POL_11001 does not conform to the Policy FW schema I've not looked at the policy spec for ages but none of those sound like we'd need actual runtime support for things like transactions, async, noListener etc so it seems like we may be able to get them all passing now with whats there in the model already, does that sound right or can someone see things that they know wont be able to be working? ...ant
