I've tried to perform a helloWorld test with Hermes and a EMS Session and the truth was that I couldn't manage to do it
In Hermes I could create a Session, connect to the EMS Server and even browse queues and topics. Everything looked fine till here.
The first problem came when trying to load the Hermes property files, soapUI do not detect the EMS Session I had created, and after verifying it, it was, in fact, configured in the Hermes config file (contained, by default, in the .hermes folder).
After, I've tried the example with the ActiveMQ, just to test if the problem could be another, and this time, no problems found, when loading the hermes config file, the Session, and its queues/topics were detected and then, I could perform a couple of calls successfully.
It'd be very useful for me to be able to perform tests with JMS transport through EMS Server to test our TIBCO Services.
At least with a very Simple helloWorld SOAP/JMS service and without exhaustive testing. But looks pretty fine.
Although, I have a question, if I may.
There isn't a way that I don't need to add the JMS endpoint? Because, when importing a WSDL with a JMS binding, such as this:
SoapUI don't make it directly available and it's necessary to posteriorly add it, and what's worst (I mean, boring), the SoapAction property needs to be added, in order to correctly invoke the service.
Despite this tiny drawback (and maybe it's just a missutilisation that I'm unfortunately doing), looks fine
If you have any recommendations or tips, they'd be very welcome
the latest nightly-build will read TIBCO bindings in these WSDLs as if they were SOAP/HTTP binding, which at least imports them correctly into soapUI, although some binding-specific settings related to JMS will have to be set manually in the UI.
Unfortunately, I've only tried the referred night-build version today. Indeed, it recognizes the binding, but still doesn't set the destination queue or even the SoapAction. Why, if it is contained in the wsdl, I don't see a reason, at least in a first analysis and not considering technical issues, to not do it. Anyway, it's good enough as it works
Despite this, the reason that bought me here today was to ask you, if there isn't a way to use temporary queues (as reply). If I don't set the replyTo JMSHeader property with an existing queue and it's not set in the URI, I couldn't manage to make it work.