How to integrate SoapUI with JMSToolBox
Hi, I'm the author of JMSToolBox (https://sourceforge.net/projects/jmstoolbox), which has similar functionnalities as HemesJMS JMSToolBox as been developepd as an alternative to HermesJMS as it see...
Forum Discussion
Just a remark on the link Rao provided, that one thing that is not always obvious regarding SoapUI plugins, is that there are actually 2 types, so called old-style plugins (designed and supported by open-source SoapUI) and the plugins as per that link (these only work with SoapUI NG i.e. they have special annotations and are compatible with the Plugin Manager, they don't work with the open source version, but could in some cases be reworked to do so).
Here is a link for plugins made for the open source version:
http://www.soapui.org/extension-plugins/old-style-extensions/deprecated-extension-plugins.html
They aren'r really any harder to develop, but there is less in the way of help docs etc. I have used Gradle to make my old-style / open source SoapUI plugins and can maybe help if this is the way you want to go, rather than the commercial SoapUI NG plugin route.
Hope this helps,
Cheers,
Rupert
Addinonal remark on plugin type - one thing I forgot to mention on this, is that I had heard few months ago that Smartbear were planning to port the SoapUI NG / new style plugin framwork back to open source SoapUI, which would be a nice move if they were to do it. Although I don't know when this might happen - maybe some from SmartBear / dev team has some news here?
Thanks everyone for your answers.
I will evaluate in the coming days if I go forward with the plugin or not, I have to find the source code for the Hermes plugin and evaluate the impacts of JMSToolBox itself
Also, for sure, if I go forward, the plugin will definitively be available for the FOSS version of SoapUI
FYI JMSToolBox is GPL v3.0 licensed
I've checked the source code of SoapUI concerning the Soap over JMS feature, it seems that HermesJMS is deeply integrated with SoapUI as you can see in this class : https://github.com/SmartBear/soapui/blob/next/soapui/src/main/java/com/eviware/soapui/impl/wsdl/submit/RequestTransportRegistry.java
I dont know how to override the "RequestTransportRegistry" as everything is hard coded and I don't think a "regular" plugin can be use to associate the JMS transport to JMSToolBox in anyway
Maybe there is a way to add an entry to this "RequestTransportRegistry" ?
Hi,
I have only had a quick look, but what you are saying regarding the limitations of the current SoapUI code and plugin architecture might mean that your best route is joining the SoapUI OS project on GitHub and maybe adding JMSToolBox as an enhancement to the core product? Have you contacted SmartBear Staff about anything like this?
It seems like a good opportunity for you to help them improve their product and I got the impression from the Hermes JMS project (and some issues gettting it to work with more recent versions of ActiveMQ) that it went dormant.
Thanks,
Rupert
Hi,
I'm not ready to go this way, and to be honest, I.'m not sure to integrate JTB code directly into SoapUI as it is done for HermesJMS is a good idea..IMHO this kind of coupling is a very bad idea, las is the installation of HermesJMS with SoapUI..
A plugin seems to be the right answer but I don't know where to start from, adding a new "transport" for the request seems the way to go but I don't know if it is possible via a plugin
