Arthur,

I included updates for component-assertion-table.xml, document-assertion-table.xml, and wsdl20.xml. These looked to be the source files to update for the assertion tables. Are there other files I should have updated?

Lawrence Mandel



Arthur Ryman/Toronto/IBM

01/09/2006 12:15 PM

To
Lawrence Mandel/Toronto/[EMAIL PROTECTED]
cc
[email protected], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject
Re: Binding, Service, Modularization, Extensibility, and Location assertionsLink




Lawrence,

Thx. I'll review and apply the patch. You only need to include the patches for the source specs, e.g. wsdl20.xml, since the other files are generated.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]



Lawrence Mandel/Toronto/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]

01/06/2006 05:14 PM

To
[EMAIL PROTECTED]
cc
[email protected]
Subject
Binding, Service, Modularization, Extensibility, and Location assertions






I've created and attached a patch for the WSDL20 folder that updates component-assertion-table.xml, document-assertion-table.xml, and wsdl20.xml to include assertions ids and entries in the assertion tables for sections 2.9-2.20, 4, 6, 7, and 8 of the WSDL 2.0 specification. I broke the assertions down as best I could into document and component assertions. When in doubt (there are some assertions that are really for service implementations) I marked them as component. It may be better to create a new type of assertion table for service implementations.




Thanks,


Lawrence Mandel


Attachment: wsdl20.patch
Description: Binary data

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to