John,
I just looked at the new design and I have a question. Description is actually very different from the other components since it respresents one or more <description> elements. Doesn't this break the assumption you're making,
i.e. that you can go to a <description> element from a Description component? I general, there are several <description> elements for a Description component.
On 11/4/05, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
John,
I'm in favour in consolidating the implementation classes wherever it won't have a negative usability impact (such as when it requires odd or confusing method names).
As for the documentation you have, I'd encourage you to post what you have to the Wiki. We can refine it later but at least this will allow people to take a look at something.
Lawrence
John Kaputin <[EMAIL PROTECTED]> 11/03/2005 04:56 PM
woden-dev
[email protected] Design change for WSDL Description implementation
I have just committed change r330632 so that now the Description andJohn Kaputin---------------------------------------------------------------------
DescriptionElement interfaces are implemented by a single class,
DescriptionImpl. Details of the design change, the rationale and a UML
class diagram are in the attached PDF. Comments welcome.
(See attached file: Design for WSDL Description.pdf)
BTW, I have various fragments of design in Word and UML that I still need
to collate into some design documentation on the website or wiki.
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]
