@gandhinath In ConductR logging is a feature which need to be enabled explictly. You can do that by starting the sandbox as:
sandbox run 1.1.2 --feature logging
This will run elastic-search and kibana as additional bundles. Make sure that you VM has sufficient memory. elastic-search uses 1 GB by default.
Afterwards you can retrieve logs of any bundle:
conduct logs my-bundle
1.1.2 is the ConductR version itself. So it was correct to use
1.1.2 with the
sandbox run command.
1.4.2 is the version of the
sbt-conductr-sandbox sbt plugin. With this plugin it is possible to use the
sandbox command directly from the sbt / activator session.
ServiceLocatorinterface. Also, it should be possible to run a Lagom service “standalone”, outside of an orchestrator (I’ll add documentation for this as soon as I have a moment). Of course, this isn’t recommended (see the itemised list in http://www.lagomframework.com/documentation/1.0.x/Overview.html for the whys), but it’s possible.
@domdorn The signaling that the application has started can be achieved in different ways:
sbt-lagom-bundleautomatically adds this library to your project.
checkcommand in the bundle configuration you can tell ConductR to check a certain task before starting the application. In this way you can achieve a similar polling mechanism as done in spring cloud with any kind of app. The bundle configuration provides samples how to create configurations for docker images and non docker images
Let me know if this is helping.
To bring this in context.
sbt-bundle is an sbt plugin that creates the bundle based on your defined settings in the
build.sbt. A bundle consist of your application classes (e.g. jars) and a
bundle.conf which is a configuration for the bundle.
sbt-bundle is creating the
bundle.conf for you.
testunder activator. I tried creating a new Lagom project and
testunder activator properly executed the tests. Tried stripping my own test lagom project to the bare minimum as provided when creating a new lagom project without success. After deleting every single
targetdirectory and rerunning
testthey did get executed though... Maybe something got messed up in there.
target/scala-2.11/src_managed/mainbeing correctly picked up by IntelliJ as being a "Source Folder". By default when importing a new Lagom project in IntelliJ that directory is not registered as a source folder. After including the Immutables library, creating an Abstract class, setting up the Annotations Processor and performing a rebuild in IntelliJ the
target/scala-2.11/src_managed/maindirectory does get created now with the class based on your Abstract class. However the
target/scala-2.11/src_managed/maindirectory is still not recognised as a source folder. In order to have IntelliJ recognise it as a source folder I had to reimport my project as an SBT project. So that's an alternative from having to manually un-exclude the
targetdirectory and marking
target/scala-2.11/src_managed/mainas being a Sources folder