[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Resolutions of Issues 80 and 95 applied and checked in.
Hi, I just checked in the document with updates for resolutions of issues 80 and 95. Looks like the site was going through some maintenance between yesterday and today, I had trouble accessing the cvs repository until now. Hopefully it was a temporary outage. While making my updates for issue 95, I noticed the first example in section 13.4 does not match up with the new restrictions brought in with the addition of @faultMessageTpe to <catch>. The spec now has this restriction, "the faultVariable and faultMessageType declarations go together, i.e., they must either both be present or both absent." However the example is shown as follows: <faulthandlers>
<catch faultName="x:foo">
<empty/>
</catch>
<catch faultVariable="bar">
<empty/>
</catch>
<catch faultName="x:foo" faultVariable="bar">
<empty/>
</catch>
<catchAll>
<empty/>
</catchAll>
</faulthandlers>
Not sure if this a known issue or if we plan to update examples in a
separate pass but, thought I would mention just in case.Oh, I hand the pen back at this point. Regards, Prasad -------- Original Message --------
Satish Thatte wrote: >Alex, welcome! Let me know that you got this message through the >mailing list channel so I can stop copying you explicitly. > >Summary of the decisions and discussion today. > >Ben and Paco will coordinate fixing both the language for 72 and the >schema for 74. They will try to finish by EOD Thursday (tomorrow). > >Prasad then gets the pen to incorporate the resolutions for 80 and 95. >Prasad, can you finish this by the weekend? > Sure, I should be able to, once I get the pen. Thanks. Prasad Yendluri wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]