ISSUE-23: What to do with start parameter in contentType

mphillip

What to do with start parameter in contentType

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Mark Phillips

Opened on:

2010-01-25

Description:

In section 2.4 we state that "if the payload is formatted as a MIME multipart message, then the first byte or character encountered in the JMS Message body MUST be the start of the MIME " but we do not state what should happen if the "start=" parameter is specified in the contentType property value


Proposal:
Suggest we state explicitly that the "start=" parameter will be ignored...

In 2.4, change:
Note also that if the payload is formatted as a MIME multipart message, then the first byte or character encountered in the JMS Message body MUST be the start of the MIME boundary for the start of the first part — what MIME Part One [IETF RFC 2045] section 2.5 calls a "Body Part".

to:
Note also that if the payload is formatted as a MIME multipart message, then the first byte or character encountered in the JMS Message body MUST be the start of the MIME boundary for the start of the first part — what MIME Part One [IETF RFC 2045] section 2.5 calls a "Body Part". If the contentType property value includes a "start" parameter then it MUST be ignored.

...and add a new assertion to check the new requirement.

Related Actions Items:

No related actions

Related emails:

1. Agenda for 2010-02-09 conference call (from eric@tibco.com on 2010-02-08)
2. Agenda for 2010-02-02 conference call (from eric@tibco.com on 2010-02-01)
3. Agenda for the 2010-01-26 conference call (from eric@tibco.com on 2010-01-25)
4. ISSUE-23 (mphillip): What to do with start parameter in contentType [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-01-25)

Related notes:

Display change log