ACTION 173 - discuss URI scheme reviewers with IBM JMS spec. contacts
Action 174 - Send some reference links to the mailin list to support this proposal
Action-160: apply test coverage proposals
Action-161: update available
Action-162 new test cases for isFault
Action-163 Contact people who are committing changes related to SOAP/JMS for the Apache CXF project
ACTION-164.ACTION-165
ACTION-168 - Develop a more detailed proposal for issue 34
Agenda for the 2010-05-04 conference call
Agenda for the 2010-05-11 conference call
Agenda for the 2010-05-18 conference call
Agenda for the 2010-05-25 conference call
ISSUE-34 (Fault sub-code QName): XML Schema should define fault sub-code QName types [SOAP-JMS Binding specification]
ISSUE-35 (Test cases with wrong delivery mode): soap-jms test-cases 0013, 0014, 0015, 0016 expected message delivery mode should be 2(PERSISTENT) [SOAP-JMS Test cases]
ISSUE-36 (Test cases with incorrect assertion references): soap-jms test-cases 1003 and 1103 should be reviewed perhaps have assertion references changed [SOAP-JMS Test cases]
ISSUE-37 (Non-fault SOAP 1.2 test cases): We should have SOAP 1.2 one-way and two-way test cases that are non fault cases [SOAP-JMS Test cases]
Minutes 2010/05/11
Minutes: 2010-05-18
Minutes: 2010-05-25
Notes from today's (2010-05-04) abbreviated meeting
Publishing "jms" URI scheme
Request To Raise Issue: soap-jms schema should define fault sub-code QName types
Request To Raise Issue: soap-jms test-cases 0013, 0014, 0015, 0016 expected message delivery mode should be 2(PERSISTENT)
Request To Raise Issue: soap-jms test-cases 1003 and 1103 should be reviewed perhaps assertion references changed
Request To Raise Issue: We should have SOAP 1.2 one-way and two-way test cases that are non fault cases
Resolution of ACTION-148 and Issue 29
Last message date: Wednesday, 26 May 2010 14:27:59 UTC