Hello... just a note about Hermes... I don't think you should be concerned about the near term longevity of the Hermes tool. In my opinion, that should not be a deal breaker. I have found that Hermes is really just a harness of the api's of JMS vendors. From SoapUI v1 to now, there really has not been a lot done on the Hermes tool and Smartbear has done a great job bundling it into their product. If Hermes did not get any more updates, it would probably work fine as is for the next ten years. Your project will be refactored at worst in 5 years. I wouldn't expect Smartbear to abandon Hermes anytime soon.
Thank you both for the quick response. The problem is I have to insure the application is supportable, likely not to have a problem is not good enough for the customer. I did locate the source for Hermes. I has a dependancy on JIDE that I was not expecting and I need to resolve any licensing issues. How did SoapUI address that. As a plan B, how difficult do you think it would be to code a Hermes substitute for just one JMS provider. We only need to support ActiveMQ. Is there any documentation available on the interface needed to implement a Hermes 'Substitute".
Champion Level 2Thanks, that is just what I need.
