As a follow-up to the post about Scaldi Play integration I would like to introduce you an integration with the Akka in this post.
Akka integration is pretty recent addition to scaldi and interestingly enough has not much to add to the core library in order to smoothly integration with the Akka. In order to use it you need to add scaldi-akka to the SBT build, so let’s do this first:
libraryDependencies ++= Seq(
"org.scaldi" %% "scaldi-akka" % "0.3.1"
In this post I would like to make small introduction to Scaldi and show you how easy it is to use it together with Play. Scaldi is dependency injection library for Scala. It’s very lightweight (without any dependencies) and provides nice Scala DSL for binding dependencies and injecting them. It’s more dynamic approach to do dependency injection in comparison to the cake pattern, because not everything is checked at the compile time. This can be seen as an disadvantage, but I personally believe, that there is place for this approach. It can be vary useful in many circumstances and many people can find it more natural (and easy), especially if they are coming from Java background.
There are only 3 most important traits that you need to know, in order to make dependency injection with Scaldi:
- Injector - it’s a container for the bindings, that you have defined in the module.
- Module - gives you nice syntax to create bindings with
Module also extends
Injector trait and implicit
Injector instance always available when you are defining your bindings
- Injectable - the only responsibility of this trait is to provide you with
inject function (so it just provides nice syntax for injecting dependencies). It’s important to understand, that it’s the only the purpose of it. So it completely stateless and knows nothing about actual bindings you have defined in the module. In order to actually find and inject dependencies,
inject function always takes an implicit parameter of type
Recently I created home page for my project Scaldi. I wanted to make it for a long time, but from the other hand I don’t want to spend much time finding some hosting and maintaining its infrastructure, making page design, etc. Github page is nice, but still I would like to have somethng more simple and unique as a project’s front page. So my main goals were:
- Use very nice feature of Github - gh-pages to host my pages
- Use markdown to create my pages without spending much time making page design
- Design that comes out-of-box should be clean and pretty
- Integrate pages generation and publishing in SBT build process