Usage

Service Discovery is enabled via configuration. See the Service Discovery Configuration section for details. To use the default Apache Curator/ZooKeeper implementation, add CuratorConfiguration configuration to your application's Configuration object. If needed, you can access the SoaDiscovery instance from SoaFeatures.

Curator

A nice side-effect of using the standard Apache Curator integration is that you can directly access the CuratorFramework instance for any other ZooKeeper usage you might have. You can even create multiple CuratorFramework instances for different ZooKeeper clusters. Each Curator instance defined in your Configuration is set in SoaFeatures with the configured name.

Adding a Custom Implementation

To use something other than the Curator Service Discovery implementation, follow these steps:

• Create implementations for SoaDiscoveryFactory and SoaExtendedDiscovery
• Add a directory named META-INF/services that contains two files: io.dropwizard.jackson.Discoverable and io.soabase.core.features.discovery.SoaDiscoveryFactory.

SoaDiscoveryFactory

Your SoaDiscoveryFactory implementation is like other Dropwizard factories. It should be both configuration and a factory. Use ZooKeeperDiscoveryFactory.java as an example. This class must be annotated with JsonTypeName and given a unique name. You then use this name as the value for the attributes type in your configuration file. E.g.

package com.me.my;

@JsonTypeName("my-discovery")
public class MyDiscoveryFactory implements SoaDiscoveryFactory {
    public String aConfigValue;

    public int anotherConfigValue;

        ...

    @Override
    public SoaDiscovery build(Environment environment, SoaInfo soaInfo)
    {
            ...
        return new MyDiscovery(...);
    }
}

SoaExtendedDiscovery

Your SoaDiscovery implementation does the actual work of Service Discovery. The details will depend on your implementation's needs. Note: your custom class should implement SoaExtendedDiscovery not SoaDiscovery. This allows your implementation to interact with the Administration Console.

ServiceLoader files

Like other Dropwizard plugins, your Service Discovery implementation needs Service Loader files. In the io.dropwizard.jackson.Discoverable file add a line containing: io.soabase.core.features.discovery.SoaDiscoveryFactory. In the io.soabase.core.features.discovery.SoaDiscoveryFactory file add a line the with fully-qualified path name of your class. E.g. com.me.my.MyDiscoveryFactory