Hi John, Sure, I'm happy to work on ElementSource. Hope I'd be able to complete it before you return :). In fact, I believe ElementSource can be used to eliminate some of the common code in the DOM/OMWSDLReaders by introducing few template methods in the BaseWSDLReader. So I will look into that aspect as well. I will keep the list updated on how it goes.
Thanks and Regards, Oshani On 7/23/06, John Kaputin <[EMAIL PROTECTED]> wrote:
Oshani, I have created a branch for WODEN-44 and in it I have created the ElementSource interface. I am away next week and don't have time to finish before then, so you can carry on developing it if you need it before then. I think from our discussions and using WSDLSource as an example you will know what's needed. I'd suggest a base class, BaseElementSource, using BaseWSDLSource as a model. Then concrete implementations - OMElementSource and DOMElementSource (I can do the DOM impl when I return, if you like). The interface may also need other methods for accessing the element's children and attributes (i.e. these will delegate to the concrete implementation's API, so they need to be common for DOM and AXIOM). Alternatively, I will be back on Mon July 31 and can continue working on this then. regards, John Kaputin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
