You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
case (service, _) => registry.unregister(service).invoke()
}).map(_ => ())
}
serviceInfo.locatableServices.foreach {
case (service, acls) =>
registry.register(service)
.invoke(ServiceRegistryService(uri, acls))
.onComplete {
caseSuccess(_) =>
logger.debug(s"Service name=[$service] successfully registered with service locator.")
caseFailure(e) =>
logger.error(s"Service name=[$service}] couldn't register itself to the service locator.", e)
}
}
}
These are very similar, but have some incidental differences, and some necessary differences due to the split javadsl and scaladsl APIs. They could be refactored to use the new ServiceRegistryClient abstraction, so that the common code can live in service-registry-client-core, and the necessary differences are encapsulated within the ServiceRegistryClient implementations.
The text was updated successfully, but these errors were encountered:
Lagom's development mode has two classes (for Scala and Java services) that implement registration with the service registry:
lagom/dev/service-registry/registration-javadsl/src/main/scala/com/lightbend/lagom/internal/server/ServiceRegistrationModule.scala
Lines 47 to 77 in 71b14a6
lagom/dev/service-registry/devmode-scaladsl/src/main/scala/com/lightbend/lagom/internal/scaladsl/registry/ServiceRegistration.scala
Lines 17 to 45 in 71b14a6
These are very similar, but have some incidental differences, and some necessary differences due to the split
javadsl
andscaladsl
APIs. They could be refactored to use the newServiceRegistryClient
abstraction, so that the common code can live inservice-registry-client-core
, and the necessary differences are encapsulated within theServiceRegistryClient
implementations.The text was updated successfully, but these errors were encountered: