Forum Discussion
olensmar_1
11 years agoContributor
Hi all,
I'm sorry about the slow reply on this; it's a confirmed bug for all annotated listener and will be fixed in the upcoming Ready API release - and also possibly in an upcoming SoapUI Pro maintenance release, although I don't know when that is planned.
You can hack around this by initializing statically in your plugin:
static
{
final SoapUIListenerRegistry registry =SoapUI.getSoapUICore().getListenerRegistry();
registry.addListener(TestRunListener.class, <yourlistenerclass>, null);
}
Hope this helps - sorry about this mistake on our side!
best regards,
/Ole
SmartBear Software
I'm sorry about the slow reply on this; it's a confirmed bug for all annotated listener and will be fixed in the upcoming Ready API release - and also possibly in an upcoming SoapUI Pro maintenance release, although I don't know when that is planned.
You can hack around this by initializing statically in your plugin:
static
{
final SoapUIListenerRegistry registry =SoapUI.getSoapUICore().getListenerRegistry();
registry.addListener(TestRunListener.class, <yourlistenerclass>, null);
}
Hope this helps - sorry about this mistake on our side!
best regards,
/Ole
SmartBear Software
Related Content
- 9 years ago
- 8 years ago
- 8 years ago
Recent Discussions
- 24 hours ago