Lawrence, I've made a lot of changes to the woden62 branch as my thoughts and code have evolved. I have made some API changes and completed a lot of the implementation, which was largely empty before.
The testcases you created now have compile breaks, but there are some issues with fixing them. Firstly, these individual assertion tests are functional tests of the WSDL spec and, like the 'good' document tests, they probably belong in the W3C WSDL 2.0 Assertion test suite as WSDL 2.0 documents. For example, Interface-1009 already exists there as testcase Interface-2B (although I'd prefer a naming convention that matches the Assertion Id). I think I'll create some sort of 'staging' area ... a new package .... in the woden test suite, where we can develop any missing WSDL testcases prior to contributing them to the WSDL 2.0 test suite via bugzilla. Once they have been added to the W3C WSDL 2.0 Assertion test suite they can be deleted from the Woden test suite. Secondly, I can't fix your testcases in their current style. The validation and assertion code has moved on from my early thoughts embodied in that initial commit to the woden62 branch. The framework doesn't support stand alone use of assertions outside of woden. Even if you go outside the API, certain constructors in the relevant implementation classes are now private or package private where instantiation is meant to be handled by the woden framework, so you can't even use the internal classes directly. The only way to test these assertions is via WSDL documents - parsing them with the WSDLReader and letting the woden framework invoke the assertion validation. There is the issue of programmatic creation of WSDL descriptions and the requirement to validate such descriptions. One approach would be a validate() method on DescriptionElement or Description or a validate(Description) type of method somewhere on the API. If this were available, your existing test cases could be fixed. However, assertions only apply to schema-valid WSDL documents, so we will need to figure out how to schema-validate programatically created WSDL before we worry about how validate assertions against it. I think that's a job for later, after we've finished validating parsed documents. regards, John. 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
