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: closing redundant tasks ------------------------------------------------------------------------------ ----- - - - == Consider Typed Collection classes == - The Woden API currently uses typed arrays to provide typesafe collections of objects. A concern was raised previously about this limiting the implementation choices for collections of objects. Consider replacing typed arrays with Woden-specific typed collection classes that hide the array implementation and maybe offer Collection or List style, typesafe accessor methods. - ==== Status ==== - Not done. - ----- - == Dereferencing objects from a 'master' collection == - Woden implementation mostly has objects dereferenced from QNames, etc, stored directly within their containing WSDL objects (one exception is schema elements and types which are dereferenced dynamically from {{{ElementDeclaration}}}, {{{TypeDefinition}}}, etc, via {{{TypesImpl}}}). Consider using an implementation similar to the {{{XmlSchemaCollection}}} class in ws-commons {{{XmlSchema}}}, that maintains a global collection of WSDL objects that are dereferenced dynamically when access is required. In this case, it is only the key (e.g. QName) that is stored in the containing WSDL object. This might make it easier to support the WSDL creation and editing use cases. - ==== Status ==== - Not done. - ----- - == Update object refs if WSDL object model changes == - Ensure that cached or dereferenced objects are cleared or modified if the WSDL object model is changed. The task above to consider using a global collection of dereferencable WSDL objects might help with this. - ==== Status ==== - Not done. - ----- == De-duplicating elements to objects == Ensure that duplicate elements are being de-duplicated to the same object correctly in the Woden implementation. ==== Status ==== @@ -187, +170 @@ Not done.[[BR]] 19Dec06: a simple resolver has been implemented, an Oasis Catalog is to follow soon. ----- - + == Consider Typed Collection classes == + The Woden API currently uses typed arrays to provide typesafe collections of objects. A concern was raised previously about this limiting the implementation choices for collections of objects. Consider replacing typed arrays with Woden-specific typed collection classes that hide the array implementation and maybe offer Collection or List style, typesafe accessor methods. + ==== Status ==== + Not done. + Closed - this will come up during API review prior to 1.0 + ----- + == Dereferencing objects from a 'master' collection == + Woden implementation mostly has objects dereferenced from QNames, etc, stored directly within their containing WSDL objects (one exception is schema elements and types which are dereferenced dynamically from {{{ElementDeclaration}}}, {{{TypeDefinition}}}, etc, via {{{TypesImpl}}}). Consider using an implementation similar to the {{{XmlSchemaCollection}}} class in ws-commons {{{XmlSchema}}}, that maintains a global collection of WSDL objects that are dereferenced dynamically when access is required. In this case, it is only the key (e.g. QName) that is stored in the containing WSDL object. This might make it easier to support the WSDL creation and editing use cases. + ==== Status ==== + Not done.[[BR]] + 19Dec06: Woden impl has now been changed to dynamically dereference qnames within the model. + ----- + == Update object refs if WSDL object model changes == + Ensure that cached or dereferenced objects are cleared or modified if the WSDL object model is changed. The task above to consider using a global collection of dereferencable WSDL objects might help with this. + ==== Status ==== + Not done.[[BR]] + 19Dec06: Closed for now. will be considered when update capability is added to the component model. + ----- == END OF CLOSED TASKS == --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
