Wednesday, 30 June 2010
Tuesday, 29 June 2010
- Minutes: 2010-06-29
- RE: Agenda for the 2010-06-29 conference call
- Agenda for the 2010-06-29 conference call
- RE: Agenda for the 2010-06-29 conference call
Monday, 28 June 2010
- ISSUE-40 (m:MaxTime in example): broken and useless reference to m:MaxTime in example in section 2.8 [SOAP-JMS Binding specification]
- NEW ISSUE: broken and useless reference to m:MaxTime in example in section 2.8
- ACTION-179 completed - fixed link to JMS URI scheme draft
- Re: Proposed resolution for Issue 39 (ACTION-182)
- Agenda for the 2010-06-29 conference call
Friday, 25 June 2010
Wednesday, 23 June 2010
Tuesday, 22 June 2010
- Minutes 2010-06-22
- Re: FYI: Updated our administrative page
- Re: Please don't rely on JMSMessageID for Protocol 2038.
Sunday, 20 June 2010
Monday, 21 June 2010
Friday, 18 June 2010
- FYI: Updated our administrative page
- Re: Please don't rely on JMSMessageID for Protocol 2038.
- Re: Please don't rely on JMSMessageID for Protocol 2038.
Wednesday, 16 June 2010
- Re: Please don't rely on JMSMessageID for Protocol 2038.
- Re: Please don't rely on JMSMessageID for Protocol 2038.
- ISSUE-39 (Protocol 2038 & correlation ID): Please don't rely on JMSMessageID for Protocol 2038 [SOAP-JMS Binding specification]
Tuesday, 15 June 2010
Monday, 14 June 2010
- Agenda for the 2010-06-15 conference call
- Proposal to resolve ISSUE-38
- (Lack of) proposal to resolve ISSUE-27
Tuesday, 8 June 2010
- ACTION-177 - Update the spec with the resolution to issue 34
- Minutes 2010-06-08
- Regrets for today's call
Monday, 7 June 2010
- Agenda for the 2010-06-08 conference call
- Action-170 completed - issue raised
- 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]
- Action-175 Clarify the test description for test 1003
- ACTION-176 -Re-write the explicit proposal for Issue 34