The name of the service that is consuming the Lagom service. This will impact how calls made through clients generated by this factory will identify themselves.
A classloader, it will be used to create the service proxy and needs to have the API for the client in it.
Releases the internal resources manages by this LagomClientFactory.
Releases the internal resources manages by this LagomClientFactory.
Stop this LagomClientFactory by shutting down the internal akka.actor.ActorSystem, Akka Streams akka.stream.Materializer and internal resources.
Stop this LagomClientFactory by shutting down the internal akka.actor.ActorSystem, Akka Streams akka.stream.Materializer and internal resources.
Convenience for constructing service clients in a non Lagom server application.
A StandaloneLagomClientFactory should be used only if your application does NOT have its own akka.actor.ActorSystem, in which this standalone factory will create and manage an akka.actor.ActorSystem and Akka Streams akka.stream.Materializer.
It is important to invoke StandaloneLagomClientFactory#stop() when the application is no longer needed, as this will trigger the shutdown of the underlying akka.actor.ActorSystem and Akka Streams akka.stream.Materializer releasing all thread and connection pools in use by the clients.
There is one more component that you’ll need to provide when creating a client application, that is a service locator. It is up to you what service locator you use, it could be a third party service locator, or a service locator created from static configuration.
Lagom provides a number of built-in service locators, including a StaticServiceLocator, a RoundRobinServiceLocator and a ConfigurationServiceLocator. The easiest way to use these is to mix in their respective Components traits.
For example, here’s a client application built using the static service locator, which uses a static URI: