Hi, there's a bunch of stuff that soapUI do not automatically obtains from the WSDL (when regarding JMS bindings). However, this isn't properly an issue since you can define as many JMS properties as you wish, and therefore you can always specify the SoapAction = "expectedSoapAction".
Obviously, it would be great that you don't need to be
tuning each request with stuff that could easy be obtained from the service's specification. Another example, the endpoint's destination from the port.
By the way, another feature that I've been waiting is the use of temporary queues (for replies). Any hope to have that feature available?
Cheers!
José Escudero
