Services overriding LagomApplicationLoader.describeService are not discovered by ConductR
See original GitHub issueReported by @aruj244 in Gitter: https://gitter.im/lagom/lagom?at=59495f9b746f1fd66322662c
override def describeServices = List( readDescriptor[HelloService] )
The
describeServices: Seq[Descriptor]
method is deprecated per the Scaladoc, anddescribeService: Option[Descriptor]
is recommended. When I try to load the hello lagom bundle to ConductR usingdescribeService: Option[Descriptor]
, it doesn’t work.conduct info
shows that the bundle is running, butconduct service-names
does not show it running. This problem goes away if I use the deprecated method instead.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Lightbend ConductR - Lagom Framework
This guide will explain how to: Start a local ConductR cluster; Conveniently package, load and run your entire Lagom system; Package Lagom services...
Read more >lagom/lagom - Gitter
Now, the problem here is while I am hitting my endpoint to add user it is not creating a table in MySQL. But...
Read more >play.api.libs.ws.ahc.AhcWSComponents Scala Example
AhcWSComponents class EchoLoader extends LagomApplicationLoader { override def load(context: LagomApplicationContext): LagomApplication = new ...
Read more >DescribeServices - Amazon Elastic Container Service
Request Parameters · cluster. The short name or full Amazon Resource Name (ARN)the cluster that hosts the service to describe. If you do...
Read more >Lagom 1.4 and Kubernetes orchestration - Yannick De Turck
Change override def describeServices to override def describeService in each ... It allows your application to perform service discovery, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Actually, let’s go ahead and close this issue (since it was originally about the specific problem reported by @aruj244 and fixed in #830) and I’ll raise new issues for follow up work.
I discovered another unfortunate surprise while working on this:
scalac
does not seem to warn when you override a deprecated method, only when you call one.There’s also no way to silence a deprecation warning, so all the
@deprecated
annotation does is increase the number of warning in the Lagom build itself (where we still call the deprecated API for backward compatibility reasons). It does not actually display a warning when building Lagom services that override the deprecated method.We will want to add a runtime warning of some kind before removing the deprecated functionality.