Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.
The following page has been changed by JohnKaputin: http://wiki.apache.org/ws/FrontPage/Woden/TaskList The comment on the change is: Update to unit test task and added new task for assertions ------------------------------------------------------------------------------ Also, create junit tests for the Service and Endpoint parsing added recently for M3. ==== Status ==== - Not done. John Kaputin expecting to do this. + John Kaputin is working on this, but other's are welcome to contribute. + Unit test so far completed for:- + {{{ServiceElement}}}, {{{EndpointElement}}}. + ----- == User documentation == Create user documentation on the woden web site explaining how to use Woden via the API. Programming model, configuration, etc. Include some code examples. @@ -129, +132 @@ WSDL spec Part 1, 2.19 QName Resolution describes looking up top level components like Interface by their QName within the Description component. The org.apache.woden.wsdl20.Description interface currently has collection methods like getInterfaces(). It also needs getters that take a QName arg like getInterface(QName). Ditto for Binding and Service. ==== Status ==== Not done. + ----- + == Sequencing and dependencies of Assertions == + We need to look at adding some form of sequencing and dependency to the assertion tests in the validation logic, where appropriate. Some asserts should happen before others. Some asserts should not be run after previous asserts have failed. + + For example, take: + * Schema-0017 (imported schema must have a targetNamespace) + * Schema-0052 (import namespace and imported targetNamespace must be equal) + + If Schema-0017 assertion fails, we should not attempt Schema-0052 assertion because it becomes redundant if we already know there is no targetNamespace. + ==== Status ==== + (jkaputin) A related discussion thread is currently running on woden-dev (at 25 Jan 06). Capturing the thought here so we don't lose it, but will probably raise JIRA when some conclusion is reached on the discussion. ----- == END of Task List ==
