SOAP/JMS WG Proposed Recommendation Disposition Of Comments

Last Update: $Date: 2011-11-01 13:40:56 $



Summary

With the exception of one issue raised against the document, all have been resolved to the satisfaction of SOAP/JMS Working Group. Previous versions of the specification also had comments which were resolved.

Almost all issues were raised by members of the working group, although sometimes as proxies for other people within the same organization as the person originating the comment/feedback.

Resolution summary below is one of the following:

Issues Closed Against Specification

ID

Raised by

Details: Title/Comments

27

Mark Phillips

Title: Link to URI specification is incorrect

Commentary: Opened, application approvedxml diff.

65

Eric Johnson

Title: Allow EXI as characterization for XML in the JMS body ?

Commentary: Opened, application approvedxml diff.

67

Phil Adams

Title: Need a SOAP 1.2-specific SOAP/JMS transport URL value

Commentary: Opened, resolved, application approvedxml diff.

68

Andrew Kennedy

Title: Broken JMS header properties example code

Commentary: Opened, resolved, application approvedxml diff

And approval by Andrew Kennedy.

69

Mark Phillips

Title: Ambiguity in spec. and potential interoperability problem with BytesMessage payload

Commentary: Opened, resolved, application approvedxml diff

70

Derek Rokicki

Title: The spec should clearly state that vendors must support both BytesMessage and TextMessage.

Commentary: Opened, resolved, application approvedxml diff



Issues Closed In Test Cases

66

Peter Easton

Title: Missing test for Protocol 2070, references to WSDLUsage assertions from various test cases

Commentary: Opened, closed