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
