ISSUE-61: Problems with SOAP samples in Appendix C

SOAP samples problems

Problems with SOAP samples in Appendix C

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Mark Phillips

Opened on:

2010-08-24

Description:

From email: http://lists.w3.org/Archives/Public/public-soap-jms/2010Aug/0017.html

There is a typo in the Appendix C SOAP JMS URI example (it uses
"jndiConnectionFactory" instead of "jndiConnectionFactoryName".

The sample messages use SOAP encoding rather than (the more fashionable)
doc-literal.

The spec would be improved if the SOAP message examples in the
specification relate to other samples - particularly if they match the
service used in the WSDL sample.


Proposal:
= = = = = =
(Note: if a new Appendix C is added which contains a full WSDL document,
then the SOAP example sections referenced in this proposal will actually be
in Appendix D)

- In Section 3.3.1, amend line 41 of the example to include more properties
in the JMS URI as follows:
<wsdl11soap11:address location=
"jms:jndi:myQueue?targetService=stockquote&amp;priority=8&amp;
replyToName=interested&amp;userprop=mystuff"/>

- (Assuming that a new Appendix C has been added which contains a full WSDL
document) - In the (new) Appendix C make the same change to the JMS URI in
the full WSDL document.

- (Assuming that a new Appendix C has been added which contains a full WSDL
document) - Add a sentence to the start of Appendix D (SOAP Samples) which
reads:
"This section contains examples of the SOAP request messages which will
be sent for the SOAP/JMS service described by the WSDL document in Appendix
C"

- Change the Example JMS URI to read:
jms:jndi:myQueue?targetService=stockquote
&priority=8
&replyToName=interested
&userprop=mystuff

- Add this sentence and two bullets after the URI example :
"The URI is augmented by the following SOAP/JMS properties from the
StockQuoteSoapJMSBinding in the WSDL:
- jndiConnectionFactoryName=sample.jms.ConnectionFactory
- deliveryMode=PERSISTENT

- In Section C.1, and C.2, change the text "The URI in Example JMS URI will
become:" to "The SOAP/JMS properties set in the URI and WSDL will be used
in the JMS message as follows:"

- In Section C.1 and C.2, in the "JMS Message Header Values" table, change
the comment for JMSDestination to read "resolved by JNDI from the
destination name myQueue"

- In Section C.1 and C.2, in the "JMS Message Properties Values" table,
change the SOAPJMS_targetService value to "stockquote" and the
SOAPJMS_requestURI value to "jms:jndi:myQueue?userprop=mystuff"

- In Section C.1 change the message example to doc-literal wrapped and make it match the WSDL example as follows:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Body>
<tns:TradePriceRequest xmlns:tns="http://example.com/stockquote.xsd">
<tickerSymbol>TickerSymbolValue</tickerSymbol>
</tns:TradePriceRequest>
</env:Body>
</env:Envelope>


- In C.2 JMS Message Properties Values table, add utf-8 to the value of the SOAPJMS_contentType field so that it reads:
multipart/related type="application/xop+xml"; boundary="MIME_boundary"; charset=utf-8

- In Section C.2 1 change the message example to doc-literal wrapped and make it match the WSDL example as follows:

--MIME_boundary
Content-Type: "application/xop+xml"; charset=utf-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <945414389.1092086011970>

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<myHdr>
<xop:Include href="cid:XXX" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
</myHdr>
</env:Header>
<env:Body>
<tns:TradePriceRequest xmlns:tns="http://example.com/stockquote.xsd">
<tickerSymbol>tickerSymbolValue</tickerSymbol>
</tns:TradePriceRequest>
</env:Body>
</env:Envelope>

--MIME_boundary
content-type:application/octet-stream
content-transfer-encoding:base64
content-id:<XXX>

YmxhaA==
--MIME_boundary--

Related Actions Items:

• ACTION-207 on Mark Phillips to Finish proposal for issue http://lists.w3.org/Archives/Public/public-soap-jms/2010Aug/0017.html - due 2010-08-31, closed

Related emails:

1. Agenda for the 2010-09-14 conference call (from eric@tibco.com on 2010-09-13)
2. ACTION-209 resolving ISSUE-61 (from M8PHILLI@uk.ibm.com on 2010-09-07)
3. Agenda for the 2010-08-31 conference call (from eric@tibco.com on 2010-08-30)
4. Fw: ISSUE-61: Problems with SOAP samples in Appendix C (from M8PHILLI@uk.ibm.com on 2010-08-27)
5. Re: ISSUE-61: Problems with SOAP samples in Appendix C (from M8PHILLI@uk.ibm.com on 2010-08-26)
6. Re: ISSUE-61: Problems with SOAP samples in Appendix C (from eric@tibco.com on 2010-08-24)
7. ISSUE-61 (SOAP samples problems): Problems with SOAP samples in Appendix C [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-08-24)

Related notes:

Display change log