Hi,I'm the author of JMSToolBox (https://sourceforge.net/projects/jmstoolbox), which has similar functionnalities as HemesJMSJMSToolBox as been developepd as an alternative to HermesJMS as it seems that HermesJMS is not maintained anymore, to get a more "modern" GUI and an easier way to define connection/sessions to Q providers.HermesJMS seems tighly coupled with HermesJMS (You can install HermesJMS at the same time a SoapUI..)I would like to develop a plugin (?) for SoapUI to be able to post/get message from SoapUI through JMSToolBoxQ:- Is there any interest for such development?- Where to start?- How to publish/maintain such extension/plugin?ThanksDenis

Sorry for the late reply guys - it wasn't because I didn't think this was interesting. It definitely is! I've been on an extended holiday and just came back. As one of the authors of the plugin framework in Ready! API (Ole Lensmar being the other), I have a strong feeling that this should be possible. However since I didn't build the JMS support and haven't worked much with it, I'm far from sure that this feeling should be trusted. Here there be dragons! The general idea is quite simple though. You need to build a plugin with a RequestTransport implementation and bind it to the prefix "jms". The class definition should look something like this: @PluginRequestTransport(protocol = "jms")public class JmsToolBoxRequestTransport implements RequestTransport { This new transport class should completely replace the Hermes based class (com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport). In theory this should, and could, Just Work (tm). In practice there may be some hardcoded dependencies on Hermes that will trip you up. We would of course do all we can (within reason) to solve any problems caused by such dependencies, including changing the SoapUI/Ready! API core to make your plugin work. I'll pass the question on to the other guys and gals in the Ready! API development team in Stockholm (some of whom know much more about the JMS support than I do), and to Ole Lensmar, the creator of SoapUI. Stay tuned! Kind regards, Manne Fagerlind, Ready! API developer

Thanks Manne and Rupert for your comments I'm a little bit confused hereCurrently my intention is to provide a plugin for the FOSS version of SoapUI (if it work for the non free version ,fine). JMSToolBox is GPL v3 licensedI definitively need to read in detail the documentation on how to develop a pluginManne, you are talking about v5.3 but the current available FOSS version of SoapUI is v5.2.1. Can I use the " Ready! API Plugin framework" with SoapUI FOSS v5.2.1?Should I understand from your comments that each time I'll build the plugin in developpement and deploy it to a local SoapUI for testing I'll need to ask you to "sign it"? or is there a dev tool to do that? or bypass the process?Also I will need to find the time to dig into all of that as the work could be split into various areas :define the way (protocol) the plugin will communicate with JTB (HTTP? REST? other?)develop a SoapUI plugin (I guess some property/config pages, "jms" protocol implementation, calls to JTB etc.)modify/extend JTB to provide/expose services/features (at least: connect, post, get, disconnect, maybe browse, discover..) called by the plugin. My initial intention is to embed as less as possible of JTB code into the plugin.I will try to find the time to setup a plugin dev environment to have an idea on what to expect in terms of development effort and impact on JTB code. I guess I could add another eclipse plugin in JTB dedicated to expose JTB services/features to other tools like SoapUI Denis aka titou10

Yes, sorry I meant 5.2.1, not 5.3. Unfortunately, if you're running with the official build of SoapUI OS, you need to sign it. However, it's quite easy to jailbreak it (it is open source, after all), so you shouldn't have to do the signing process during development. Here's a solution by another plugin developer: https://github.com/hschott/soapui-pluginloader-jailbreak. Another solution is to just test with an earlier version of SoapUI. I believe the signing requirement was introduced in 5.2.1. As I said, we're currently discussing what the long-term solution will be, so this problem is likely to go away pretty soon. Resources for plugin development can be found on this page: http://community.smartbear.com/t5/SmartBear-Developer-Network/ct-p/SmartBear_Developer_Network. You may also want to check the forum for plugin development, where you can also post your own questions, of course: http://community.smartbear.com/t5/Ready-API-and-SoapUI-PlugIn/bd-p/Ready_SoapUI_Plugins I don't understand the part about communication with JTS. Doesn't it have a a Java library that you can call into to communicate with it? You shouldn't have to embed any JTS code into the plugin, because the plugin framework supports bundling libraries inside the plugin JAR. If you have any more questions, don't hesitate to ask! Regards, Manne

As a matter of fact, the Ready! API Plugin framework is now also part of SoapUI OS (I believe it was added in 5.3). However, the plugins written using this framework (which is much easier and safer to use than the old extension mechanism) have to be signed by us. This is an interim solution to make sure that people don't try to load plugins into SoapUI OSthat would only work in Ready! API. The latter has a lot of functionality and platform services that are missing in the OS version, e.g. an event bus that allows plugins to get notifications from other parts of the application. We also want to review plugins contributed by the community, just like we review Pull requests on GitHub. Long term I don't expect plugins to have to be signed by us, but until we find a better model, we're happy to help you with signing your plugin. Regards, Manne

I've finaly developped a basic plugin to communicate with JMSToolBox (in draft state..)I've implemented a new protocl ("jtb") that allows to communicate with JMSToolBox via its exposed REST interface Bascially this allows to deal with messages (post, get, etc.) and destinations defined in JMSToolBoxAs an example, the endpoint "jtb://localhost:9997/rest/message/sessionMQ/queue1" to post the message to the corresponding session/destinationThe goals is to become an alternative to HermesJMS but I don't know what kind of exchanges between SoapUI and the Q Manager via JMSToolBox I should implementCurrently, the services are a kind of "post and forget", ie call the REST service to post/get/etc, a message to a queue and that's it.The HermesJMS integration offer more options (post, post then get etc.), however the JMSToolBox exposed services have more diversity to deal with Q Managers and Destination (Topics/Queues)I would like to know what are the real use-cases to use a JMS Client from SoapUI in order to add them to the plugin and if there are people relly interested in such a plugin

How to integrate SoapUI with JMSToolBox

21 Replies

rupert_anderson
Valued Contributor
9 years ago
Hi,

This is an cool idea, as you say the Hermes project seems to be dormant.

I would be happy to offer advice / snippets to show you how to develop a basic SoapUI plugin or even work with you to maybe help develop yours (amoungst other things I'm a Java Dev / Architect, have done some simple plugins, but not published any).

Aside from the plugin fundamentals, you would most likely need some java Swing skills to cover any UI feautres.

However, whilst I might be able to help, in all honesty a stronger offer may come from the Smartbear / SoapUI development team...?

Aside from the actual coding there are probably some architectural / design aspects to consider before starting the plugin, like whether you see it being a custom JMS TestStep plugin or whether you would like it to extend the existing Request TestSteps?

Apart from being done as a plugin, if seen as core functionality, possibly the Smartbear team would allow / help it to be added as a enhancement to the actual product e.g. as part of a feature request?

Anyway, cool idea, let me know if I can help and/or good luck working on it!

Cheers,

Rupert
nmrao
Champion Level 3
9 years ago
titou10, Nice to see this thread.

Here is the starting point

http://www.soapui.org/extension-plugins/developing-plugins/plugin-development.html

I believe it would be good to be on github.

By the way, does jmstoolbox support jms 2.0?

Wish you good luck.
- rupert_anderson
  Valued Contributor
  9 years ago
  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
  - rupert_anderson
    Valued Contributor
    9 years ago
    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?
- titou10
  Occasional Contributor
  9 years ago
  Yes JMSToolBox is bundled with the JMS 2.0 API

Forum Discussion

How to integrate SoapUI with JMSToolBox

21 Replies

Related Content

SoapUI Report Integration SSIS

Integrate TestComplete in SOAPUI

Matlab AppDesigner CEF-based application integration

Integration with Azure DevOps failed

Selenium/Cucumber Integration

Recent Discussions

Will SOAP UI 5.6.1 work with JDK 8

clone TestSuite fails when there are more project with the same name

SOAP Request works in SoapUI, but not in C# code

How to configure Swagger in Paas to use it in Oracle APEX instance.

log4j1.x vulnerability