ISSUE-1 Assert Protocol-2013 is spurious
CLOSED
Assertion Protocol-2013 is missing RFC 2119 language
2009-07-27
SOAP-JMS Binding specification
0
ISSUE-2 Protocol-2020 is spurious
CLOSED
Assertion Protocol-2020 missing RFC 2119 language
2009-07-27
SOAP-JMS Binding specification
0
ISSUE-3 Protocol-2023 is spurious
CLOSED
Assertion Protocol-2023 missing RFC 2119 language
2009-07-27
SOAP-JMS Binding specification
0
ISSUE-5 Protocol-2035 is redundant
CLOSED
Protocol-2035 is redundant
2009-07-27
SOAP-JMS Binding specification
0
ISSUE-6 Protocol 2039 redundant
CLOSED
Protocol 2039 redundant, missing RFC 2119 language
2009-07-28
SOAP-JMS Binding specification
0
ISSUE-7 Protocol-2041 is spurious
CLOSED
Protocol-2041 is spurious
2009-07-29
SOAP-JMS Binding specification
0
ISSUE-8 Incorrect example, section C2
CLOSED
Example in C2 contrary to Protocol-2029
2009-07-29
SOAP-JMS Binding specification
0
ISSUE-9
CLOSED
Clarify wording of assertions that deal with fault subcodes
2009-08-10
SOAP-JMS Binding specification
0
ISSUE-10 redundant assertions 2016 and 2017
CLOSED
Combine redundant assertions 2016 and 2017
2009-08-10
SOAP-JMS Binding specification
0
ISSUE-11 requestURI in response message?
CLOSED
Should SOAPJMS_requestURI be in the response message?
2009-08-24
SOAP-JMS Binding specification
0
ISSUE-12 Bad MIME terminating boundary
CLOSED
MIME multipart terminating boundary incorrect in Example C2
2009-09-15
SOAP-JMS Binding specification
0
ISSUE-13 Extra space in Schema
CLOSED
Soapjms schema issue
2009-09-23
SOAP-JMS Binding specification
0