We’‘ve found a small bug in the search plugin: it keeps responding to Service Discovery requests, even when it’‘s disabled. It’'s easily fixed by including the serviceEnabled attribute in the if-conditions on lines 203 and 220.
Hi Guus,
That was actually intentional on my part, I wanted to just disable the searching and not the service itself. To completely disable the service/component it would probably be better do something similiar to what is done in the destroyPlugin method, “componentManager.removeComponent(serviceName);”. Maybe there needs to be an additional level of granularity that can be set in the Admin Console that does remove the service?
Thanks,
Ryan