- From: Phil Adams <phil_adams@us.ibm.com>
- Date: Fri, 25 Jul 2008 12:33:55 -0500
- To: public-soap-jms@w3.org
- Message-ID: <OFAFB4F8F3.DE901EC0-ON86257491.005F3C80-86257491.00607DDF@us.ibm.com>
Hi everyone: Here's my stab at completing ACTION-16. I apologize for getting this out so late in the week, but that other work that I get paid for just keeps getting in my way :) Also, I spent a couple of hours trying to adapt the WS-Addressing testcase writeup (located here: http://www.w3.org/2002/ws/addr/testsuite/testcases/) for our use, but had to give up on it for now so I'll just provide a text-based writeup for these first couple of testcases. I think the WS-Addressing approach should eventually work fine though. If someone else wants to take a stab at putting the testcases below into that form, that would be great. I tried to structure the testcases like the WS-Addressing testcases. Hopefully, these can get us started with discussions, etc. for writing up our testcases. Fire away....... ******************************************************************************************************************************** SOAP over Java Message Service 1.0 - Testcases test0001 - One-way request message sent to a destination queue test0002 - Two-way request sent to a destination queue Note: "A" refers to a "Requesting SOAP Node" as described in the spec. "B" referes to a "Responding SOAP Node" as described in the spec. --------------------------------------------------------------------------------- test0001 - One-way request message sent to a destination queue Assertions: 2003 2004 2009 2010 2016 2018 2021 2022 2027 2029 2034 2036 2051 A one-way SOAP request message is sent to a destination queue. 1. A sends a message to a destination queue and the message is received by B. A uses an endpoint location URL such as: jms:jndi:jms/MyQueue&jndiConnectionFactoryName=jms/MyCF&targetService=MyOneWayPortComponent - jmsmsg:MessageType=jms_bytes (not sure how to represent this) - jmsmsg:JMSMessageID=<message id> - jmsmsg:JMSDeliveryMode=2 - jmsmsg:JMSPriority=4 - jmsmsg:JMSExpiration=0 - jmsmsg:JMSReplyTo=null - jmsmsg:JMSCorrelationID=null - jmsmsg:JMSDestination=<identifier of destination queue> - jmsmsg:JMSRedelivered=false - jmsmsg:SOAPJMS_bindingVersion="1.0" - jmsmsg:SOAPJMS_targetService="MyOneWayPortComponent" - jmsmsg:SOAPJMS_contentType="text/xml" - jmsmsg:SOAPJMS_soapAction="" - jmsmsg:SOAPJMS_requestIRI="jms:jndi:jms/MyQueue" - jmsmsg:JMSMessageBody=<contents of SOAP request message> --------------------------------------------------------------------------------- test0002 - Two-way request sent to a destination queue Assertions: 2003 2004 2009 2010 2016 2018 2021 2022 2027 2029 2034 2036 2037 2038 2040 2050 A two-way SOAP request message is sent to a destination queue. 1. A sends a message to a destination queue and the message is received by B. A uses an endpoint location URL such as: jms:jndi:jms/MyQueue&jndiConnectionFactoryName=jms/MyCF&targetService=MyTwoWayPortComponent - jmsmsg:MessageType=jms_bytes (not sure how to represent this) - jmsmsg:JMSMessageID=<message id1> - jmsmsg:JMSDeliveryMode=2 - jmsmsg:JMSPriority=4 - jmsmsg:JMSExpiration=0 - jmsmsg:JMSReplyTo=<identifier of response queue> - jmsmsg:JMSCorrelationID=null - jmsmsg:JMSDestination=<identifier of destination queue> - jmsmsg:JMSRedelivered=false - jmsmsg:SOAPJMS_bindingVersion="1.0" - jmsmsg:SOAPJMS_targetService="MyTwoWayPortComponent" - jmsmsg:SOAPJMS_contentType="text/xml" - jmsmsg:SOAPJMS_soapAction="" - jmsmsg:SOAPJMS_requestIRI="jms:jndi:jms/MyQueue" - jmsmsg:JMSMessageBody=<contents of SOAP request message> 2. B processes the request and sends a reply message to the reply queue, and the reply message is then received by A. - jmsmsg:MessageType=jms_bytes (not sure how to represent this) - jmsmsg:JMSMessageID=<message id2> - jmsmsg:JMSDeliveryMode=2 - jmsmsg:JMSPriority=4 - jmsmsg:JMSExpiration=0 - jmsmsg:JMSReplyTo=null - jmsmsg:JMSCorrelationID=<message id1> - jmsmsg:JMSDestination=<identifier of response queue> - jmsmsg:JMSRedelivered=false - jmsmsg:SOAPJMS_bindingVersion="1.0" - jmsmsg:SOAPJMS_contentType="text/xml" - jmsmsg:JMSMessageBody=<contents of SOAP reply message> ******************************************************************************************************************************** Regards, Phil Adams WebSphere Development - Web Services IBM Austin, TX email: phil_adams@us.ibm.com office: (512) 838-6702 (tie-line 678-6702) mobile: (512) 750-6599
Received on Friday, 25 July 2008 17:34:57 UTC