omrzljak
15 years agoOccasional Contributor
More controle over JMS message type needed
Hello,
JMS support for JMS test cases and mock service (as described in http://www.eviware.com/forums/index.php?topic=3129.0 ) works well with JMS services using JMS Text message. You can easy switch between http and jms transport and all your test case are still useful.
Problem is when a (not soapui ) client or service use jms byte messages (such as IBM WCF Channel for MQ) as transport. The problem in soapui is that response soap message which is of type byte message is put in response attachment. That makes it impossible for use with response assertions. Also when we call (from a soapui test case) a JMS service which requires jms byte message we have to make a test request with soap message in attachment which makes the usage of request validation and dynamic params impossible.
In http://www.soapui.org/tutorials/jms/jms-tutorial.html is described how soapui decides when to make byte message.
Why is JMSMessagType request param ignored in this case? That should be the way to control what type of message is made.
How can I prevent soapui to set soap response from byte message in a attachment (in response)?
JMS support for JMS test cases and mock service (as described in http://www.eviware.com/forums/index.php?topic=3129.0 ) works well with JMS services using JMS Text message. You can easy switch between http and jms transport and all your test case are still useful.
Problem is when a (not soapui ) client or service use jms byte messages (such as IBM WCF Channel for MQ) as transport. The problem in soapui is that response soap message which is of type byte message is put in response attachment. That makes it impossible for use with response assertions. Also when we call (from a soapui test case) a JMS service which requires jms byte message we have to make a test request with soap message in attachment which makes the usage of request validation and dynamic params impossible.
In http://www.soapui.org/tutorials/jms/jms-tutorial.html is described how soapui decides when to make byte message.
Why is JMSMessagType request param ignored in this case? That should be the way to control what type of message is made.
How can I prevent soapui to set soap response from byte message in a attachment (in response)?