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: status updates (02Feb06) and reorg tasks into open and closed lists ------------------------------------------------------------------------------ Here are some of the outstanding tasks for the Woden project. Initially, this is just a brain dump to capture known To Do's in one place. Anyone interested in contributing to the development of Woden can start with this list to see what needs doing, however the list is not necessarily 'complete'. Contributors may identify other interesting pieces of work not listed here. Notify [email protected] if you want to take ownership of any of these tasks and update the Status section below. - This list will be updated as development progresses. Anyone can update it. Tasks can be removed as they are completed. Tasks which raise important issues or involve significant work should be raised as JIRA issues. + This list will be updated as development progresses. Anyone can update it. As tasks are completed they should be moved from the Open Tasks list to the Closed Tasks list at the end of this page. Tasks which raise important issues or involve significant work should be raised as JIRA issues. + ------- + == Open Tasks:- == ----- == WSDL <import> and <include> == Due for Milestone 3. Implement parsing of <import> and <include> WSDL elements into the {{{ImportElement}}} and {{{IncludeElement}}} objects and abstract (flatten) this document composition structure into the properties of the top level {{{Description}}} component. Add junit test cases for this functionality to the Woden test suite. ==== Status: ==== - Not started. John Kaputin expecting to do this. + 02Feb06: John Kaputin has implemented the Element parsing and component model logic, but not yet created the junit tests. ----- == Extended Interfaces == Due for Milestone 3. Implement parsing of the ''extends'' attribute of the <interface> element and within the containing {{{InterfaceElement}}} object resolve the QName references to the extended {{{InterfaceElement}}} objects. Likewise for the {{{Description}}} component, resolve the extended {{{Interface}}} components. Add junit test cases for this functionality to the Woden test suite. ==== Status: ==== - John Kaputin is working on this. + 02Feb06: Didn't make M3, will be re-targetted for M4. ----- == Junit tests for parsing == Due for M3. Add junit testcases to the Woden test suite for the parsing logic implemented so far for Description, Types, Interface, Binding, Documentation, Property, Feature. Also, create junit tests for the Service and Endpoint parsing added recently for M3. ==== Status ==== - John Kaputin is working on this, but other's are welcome to contribute. + John Kaputin is working on this, but other's are welcome to contribute. - Unit test so far completed for:- - {{{ServiceElement}}}, {{{EndpointElement}}}. + + 02Feb06: Unit tests completed for {{{ServiceElement}}}, {{{EndpointElement}}} (in SVN, but did not make M3 build). - ----- - == 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. - ==== Status ==== - Not done. John Kaputin should probably start this. ----- == Developer documentation == Create technical architecture and design documentation on the Woden web site, including alternatives, rationale, etc. @@ -144, +141 @@ ==== 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 == + == END of Open Tasks == + ------- + ------- + == Closed Tasks:- == + + ----- + == 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. + ==== Status ==== + 02Feb06: The User Guide now on the web site. It reflects current development. Work to expand and restructure will be ongoing. + ----- + == END of Closed Tasks == +
