Yes it really is that simple. There are several examples of doing this in Goode.
Look at the Extensions SPI. It could easily be pulled out into a geode-spi project for a separate artifact. It uses a ServiceLoader in the XML config to resolve namespaces to an extension parser that can then create extension that can connect to the Cache or Regions in the configuration tree. There is some basic lifecycle management there too. -Jake > On Jan 8, 2019, at 3:52 PM, Dale Emery <dem...@pivotal.io> wrote: > > We are exploring adding one or more public Service Provider Interfaces (SPIs) > for Geode, and would like some guidance about standards, conventions, > precedent, and such. > > Do we have standards or conventions for creating SPIs? Good examples? Bad > examples? > > Are there standards or conventions described elsewhere (e.g. Spring) that we > should consider when defining SPIs? > > Is it as simple(!) as defining a service interface, then using Java's > ServiceLoader mechanism to discover and load instances of it? > > Any additional considerations for adding a public SPI, compared to a private > one? > > Cheers, > Dale >
