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: capture task as JIRA ------------------------------------------------------------------------------ == De-duplicating elements to objects == Ensure that duplicate elements are being de-duplicated to the same object correctly in the Woden implementation. ==== Status ==== - Not complete yet. + Not complete yet.[[BR]] + 19Dec06: JKaputin to investigate this further to see if a JIRA is needed - will then close this task. - ----- - == Refactor Component builder logic == - The {{{ComponentBuilder}}} class is used to populate properties of the WSDL Component model from the Element model when the toComponent() method is called on the {{{DescriptionElement}}}. Some of this behaviour is also present in the parseXXXX methods in WSDLReader because it's easier to handle this at parse-time when we have the necessary object references. Consider eliminating the {{{ComponentBuilder}}} class by refactoring its logic, maybe directly into the Impl classes. - ==== Status ==== - Not done. ----- == Obtain an ErrorReporter or ErrorLocator via the API == Provide the ability to obtain an {{{ErrorReporter}}} object via some type of factory method on the API to avoid the need to use {{{new ErrorReporterImpl}}}. This must accomodate any user configuration such as custom {{{ErrorHandler}}}. A problem has arisen in some Classes that are included in the API that need to report errors - they create an error reporter instance (to avoid excessive passing of object references via method args), but they must not expose any Impl classes. Hence the need for a factory mechanism. A similar requirement exists for {{{ErrorLocator}}}. ==== Status ==== - Not done. + Not done.[[BR]] + 19Dec06: JKaputin to investigate this further to see if a JIRA is needed - will then close this task. ----- + - == General type system support == - Woden currently supports just the XML Schema type system. As per the WSDL 2.0 spec, some form of more general, extendible type system support is required to cater for non-XML Schema type systems. - ==== Status ==== - Not done. - ----- == Improve the API javadoc == Much of the javadoc for the interfaces and classes that comprise the Woden API is out of date, incomplete or insufficient. This needs to be addressed. ==== Status ==== @@ -188, +181 @@ Not done.[[BR]] 19Dec06: Closed for now. will be considered when update capability is added to the component model. ----- + == Refactor Component builder logic == + The {{{ComponentBuilder}}} class is used to populate properties of the WSDL Component model from the Element model when the toComponent() method is called on the {{{DescriptionElement}}}. Some of this behaviour is also present in the parseXXXX methods in WSDLReader because it's easier to handle this at parse-time when we have the necessary object references. Consider eliminating the {{{ComponentBuilder}}} class by refactoring its logic, maybe directly into the Impl classes. + ==== Status ==== + Not done. [[BR]] + 19Dec06: done in a previous milestone release (still some extensions code to be refactored) + ----- + == General type system support == + Woden currently supports just the XML Schema type system. As per the WSDL 2.0 spec, some form of more general, extendible type system support is required to cater for non-XML Schema type systems. + ==== Status ==== + Not done.[[BR]] + 19Dec06: replaced by JIRA WODEN-114. + ----- + == END OF CLOSED TASKS == --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
