ISSUE-70: The spec should clearly state that vendors must support both BytesMessage and TextMessage.

Derek

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

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Derek Rokicki

Opened on:

2011-01-11

Description:

As discussed in our last meeting, the spec may not be clear as to how and when vendors must support the different JMS message types.

Section 2.4 says, "The contents of the JMS Message body MUST be the SOAP payload as a JMS BytesMessage or TextMessage." This statement does not make it clear that the receiving node (i.e. web service provider) must support both message types. Requiring support for both message types can be inferred in section 2.6.2.3, however it is probably best if we spell this out clearly earlier in the spec.

I propose we add the following statement to section 2.4, "while the requesting node can support either BytesMessage or TextMessage, the receiving node MUST support both BytesMessage and TextMessage."

Related Actions Items:

No related actions

Related emails:

1. Agenda for the 2011-01-18 conference call (from eric@tibco.com on 2011-01-17)
2. Completed ACTION-240, applied changes for ISSUE-70 (from eric@tibco.com on 2011-01-17)
3. Minutes 2011-01-11 (from M8PHILLI@uk.ibm.com on 2011-01-11)
4. ISSUE-70 (Derek): The spec should clearly state that vendors must support both BytesMessage and TextMessage. [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2011-01-11)

Related notes:

Display change log