(Lack of) proposal to resolve ISSUE-27
Action-169 Apply resolutions for Issues 35-37
Action-170 completed - issue raised
Action-175 Clarify the test description for test 1003
ACTION-176 -Re-write the explicit proposal for Issue 34
ACTION-177 - Update the spec with the resolution to issue 34
ACTION-179 completed - fixed link to JMS URI scheme draft
Agenda for the 2010-06-08 conference call
Agenda for the 2010-06-15 conference call
Agenda for the 2010-06-22 conference call
Agenda for the 2010-06-29 conference call
Fwd: Re: Updating namespace page link
FYI: Updated our administrative page
ISSUE-38 (WSDL 2.0 --> non-normative): WSDL 2.0 support not going to be properly tested by implementations, so should be non-normative. [SOAP-JMS Binding specification]
ISSUE-39 (Protocol 2038 & correlation ID): Please don't rely on JMSMessageID for Protocol 2038 [SOAP-JMS Binding specification]
ISSUE-40 (m:MaxTime in example): broken and useless reference to m:MaxTime in example in section 2.8 [SOAP-JMS Binding specification]
Minutes 2010-06-01
Minutes 2010-06-08
Minutes 2010-06-22
Minutes: 2010-06-29
NEW ISSUE: broken and useless reference to m:MaxTime in example in section 2.8
Please don't rely on JMSMessageID for Protocol 2038.
Proposal to resolve ISSUE-38
Proposed resolution for Issue 38 (ACTION-182)
Proposed resolution for Issue 39 (ACTION-182)
Regrets for today's call
Today's (6/1/2010) SOAP/JMS meeting - informal at best
Last message date: Wednesday, 30 June 2010 14:31:41 UTC