Peter, Your understanding about the programming model and ExtensionRegistrar are correct.
The validator is at an early implementation stage. We will work our way through the WSDL 2.0 assertions, adding to the implementation as we go. We started on the Description and Interface assertions just to verify that the API works. The implementation will be a work in progress up to the M8 release. In other words, the API is probably stable now but the implementation is not yet finished (I say 'probably' because we need to implement a broader range of assertions first to test that our API design is sufficient). Some of the cross-ref checks may need to be done via the Element API, rather than the Component API, but note that on the Woden wiki we have an API issue pending about collapsing these two APIs into a single WSDL API. I have been and will be pretty busy on other matters until April, so progress on M8 has slowed down, but it is still in plan. The initial assertion work was done in a separate branch until we felt we had the API stable enough to move it into trunk. Work will continue in trunk. Feel free to contribute if you have time and interest. It should be easy to do this piecemeal, one assertion at a time. I will try to get some explanation of assertions documented soon. regards, John Kaputin "Peter Danielsen" <[EMAIL PROTECTED]> wrote on 19/03/2008 23:24:37: > Hi, > > I'm curious about the stability of the Assertion design in Woden. > > I've been looking at it from the point of view of an extension and I > think this is the procedure: > > 1. Create a class that implements org.apache.woden.wsdl20.validation.Assertion > for each class that is affected by an assertion. > a. Implement "getId()" > b. Implement "validate(Object, WodenContext)" > > 2. Register each Assertion class by calling ExtensionRegistry. > registerAssertion passing an instance of the Assertion class and the > affected class. This would likely be done from an ExtensionRegistrar. > > That seems reasonable, but the reason I asked about the stability is > that when I look at the validate method of org.apache.woden. > internal.wsdl20.validation.WSDLValidator > I see that it's not checking assertions on Binding or Service > elements. Their absence made me wonder whether this is still in an > early design stage? > > Also, I'm assuming that cross-checks between elements (e.g. > <interface> and <binding> ) will be the responsibility of the "more > detailed" element (<binding> in this case) and that that element's > Assertion may require navigation of the containing elements to do > its work. Is that correct? > > Any references or explanations on the conventions and use of > Assertions would be very useful. > > Thanks, > > Peter 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]
