Lazy container wrapper aims to solve the problem of cross-container dependencies in MultipleContainers when a second container
requires some after start data from a first one (e.g. an application container needs JDBC url of a container with a database - in that case
the url becomes available after the database container has started)
You don't need to wrap your containers into the LazyContainer manually
when you pass your containers in the MultipleContainers- there is implicit conversion for that.
Lazy container wrapper aims to solve the problem of cross-container dependencies in
MultipleContainers
when a second container requires some after start data from a first one (e.g. an application container needs JDBC url of a container with a database - in that case the url becomes available after the database container has started)You don't need to wrap your containers into the
LazyContainer
manually when you pass your containers in theMultipleContainers
- there is implicit conversion for that.