Forum Discussion
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
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 JMSToolBox
As an example, the endpoint "jtb://localhost:9997/rest/message/sessionMQ/queue1" to post the message to the corresponding session/destination
The 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 implement
Currently, 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
Related Content
- 9 years agovon_bailey
- 4 years agoLarsenrw22
- 8 years agoAndyO
- 6 years agokaivi
Recent Discussions
- 5 days agoemoya