Fw: ISSUE-10: update available

Of course, once I sent out the email below, I noticed a minor problem with 
the change I made.    I neglected to include the entire 2-sentence passage 
inside the requisite "assert" element in the soapjms.xml file that would 
cause the entire passage to be included in the assertion table in Appendix 
E.      So, I've made that additional change in revision 1.62 of 
soapjms.html:
http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.62&content-type=text/html;%20charset=utf-8#Protocol-2016

The total changes for this issue can be viewed here (revs 1.61 and 1.62):
http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.html.diff?r1=1.60&r2=1.62&f=h


Phil 
__________________________________________________________________________________________________________ 

Phil Adams (phil_adams@us.ibm.com)

WebSphere Application Server
Office: (512) 286-5041 (t/l 363)
Web Services Development
Cell: (512) 750-6599
IBM - Austin, TX


----- Forwarded by Phil Adams/Austin/IBM on 08/18/2009 04:53 PM -----

From:
Phil Adams/Austin/IBM@IBMUS
To:
public-soap-jms@w3.org
Date:
08/18/2009 04:01 PM
Subject:
ISSUE-10: update available
Sent by:
public-soap-jms-request@w3.org




Hi everyone, 
I've committed the changes for ISSUE-10 (consolidation of assertion 2017 
with 2016).   Version 1.61 of the binding spec contains these changes: 
http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.61&content-type=text/html&f=h 


Changes from the previous revision: 
http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.html.diff?r1=1.60&r2=1.61&f=h


Phil 
__________________________________________________________________________________________________________ 

Phil Adams (phil_adams@us.ibm.com) 

WebSphere Application Server 
Office: (512) 286-5041 (t/l 363) 
Web Services Development 
Cell: (512) 750-6599 
IBM - Austin, TX 

Received on Tuesday, 18 August 2009 21:59:09 UTC