lagom | A Jekyll blog theme with just the right amount of style | Theme library

It seems that the real cause for the exception was because I should have added logic for handling the event as follows: in helloEvents(), I needed to add logic similar to the following:

Your object CustomPostgresProfile extends PostgresProfile instead of CustomPostgresProfile. If you fix that, it works.

Writing to a file in a container is bad for two reasons: 1. Logs are available only within the container i.e.,would require to get into the container to see the logs 2. They are not available via kubectl log command 3. They are ephemeral in nature i.e., if container crashes, logs will disappear

Instead writing to STDOUT and STDERR is considered as best practise in a container environment. The logs written to STDOUT and STDERR are redirected by docker engine to a location in the node (/var/log/containers/). Moreover, these logs are also available via kubectl logs command.

Practically logs are not even preserved at even a node but are instead moved to a central logging system. You can read more about it here.

I think that you shouldn't have a different entity 'Transactions' because it is tightly coupled to the account entity, in fact, the transactions of an account is no more than the event log of this account. So I recommend persisting the balance with a unique transaction id and the id of the other account when it is a transfer transaction, and make the read processor to listen the events of the account changes to store them in the read model.

Doing this, a transfer is just a message between the two accounts that results in a modification of the balance that later will be persistent as part of the event log of each of them. This way seems more natural and you don't have to manage a sepparate aggregate root that, in addition, is tightly coupled to the account entities.

I was calling the wrong method. The openApiGenerators just list the generators which is what it was doing. To generate the output, you have to call the task created above openApiGenerate. Thanks @philonous for the answer.

According to default Play project layout application.conf located at conf/application.conf. So if you will inject play.api.Configuration this will represent parsed and loaded config from that file.

On another hand I suppose, Lagom is library, which relies on default Maven project layout, which differs from default Play layout, in which src/main/resources is standard folder for resources like configuration, which is why in Lagom project example you see application.conf in another folder then in Play.

What you can do as an option: take play.api.Configuration.underlying and pass manually to Lagom code.

Or keep using standard Maven project layout for Play via special plugin introduced after version 2.6.8: https://www.playframework.com/documentation/2.6.x/Highlights26#PlayService-sbt-plugin-(experimental)

Hope this helps!

You need to create your custom exception that must be inherited from TransportException:

In the first request, you are logging in using HTTP Basic authentication. Does the site that you're using support HTTP basic authentication? Typically when a site does support it, it won't send you a cookie, rather, it will expect the login credentials to be sent with every request. So, when using HTTP basic authentication, there should be no need to login at the login URL, instead, add the username and password to the request to queryUrl. If that doesn't work, then that could mean the site you are making requests on doesn't support HTTP Basic authentication.

The other type of login is to submit the username and password in a login form, and then site you are logging into will send you back a cookie which you can use for subsequent requests. That appears to be what you're trying to do, but to do that, you can't use the withAuth method, rather, you have to find out what the username/password parameters are in the sites login form, and send a form with those parameters set. I can't tell you what those parameters are, that is entirely dependent on the site you're logging into, you'll have to look at the documentation for that site, or at the HTML it outputs on the login page. When you get back the response to the login request, you should check the response code to see if it was successful. The documentation for how to submit form parameters using Play WS can be found here, here's an example of what it might look like:

I've used Lightbend config to configure Lagom services via environment variables in docker containers for many years, so know that it can be done and has been pretty straightforward in my experience.

With that in mind, when you say that they're not used by application.conf, do you mean that they're unset? Note that unless you're passing a very specific option as a Java property, configuration.getString("ENV_MYSQL_DATABASE_URL") will not read from an environment variable, so checking that will not tell you anything about whether mysql.url is affected by the environment variable. configuration.getString("mysql.url") will give you a better idea of what's going on.

I suspect that in fact your Docker image is being built with the dev-mode properties hardcoded in, and since Java system properties take precedence over everything else, they're shadowing the environment variable.

You may find it useful to structure your application.conf along these lines: