Forum Discussion
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
Hi Manne,
That sounds cool, I like the idea that the plugins may one day not need to be signed, at least for the open source version :-)
I didn't realise there was a 5.3 version of open source SoapUI, or is this a next release? If so, do you know when it might be available? Sounds very sensible to unify the plugin frameworks anyway.
Thanks,
Rup
- MFagerlind10 years ago
Staff
Sorry, I slipped: I meant 5.2.1. Mostly working with Ready! API at the moment. :-)