Wednesday, 26 May 2010
Tuesday, 25 May 2010
- Action 174 - Send some reference links to the mailin list to support this proposal
- Minutes: 2010-05-25
- Resolution of ACTION-148 and Issue 29
- Agenda for the 2010-05-25 conference call
Monday, 24 May 2010
- ACTION-168 - Develop a more detailed proposal for issue 34
- Re: Publishing "jms" URI scheme
- Publishing "jms" URI scheme
Tuesday, 18 May 2010
- Minutes: 2010-05-18
- Action-163 Contact people who are committing changes related to SOAP/JMS for the Apache CXF project
Monday, 17 May 2010
Tuesday, 18 May 2010
Monday, 17 May 2010
- Re: Request To Raise Issue: We should have SOAP 1.2 one-way and two-way test cases that are non fault 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]
- 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-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]
- Re: Request To Raise Issue: soap-jms schema should define fault sub-code QName types
- ISSUE-34 (Fault sub-code QName): XML Schema should define fault sub-code QName types [SOAP-JMS Binding specification]
- Request To Raise Issue: We should have SOAP 1.2 one-way and two-way test cases that are non fault cases
- Request To Raise Issue: soap-jms test-cases 1003 and 1103 should be reviewed perhaps assertion references changed
- 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 schema should define fault sub-code QName types