PART A
I have a work reflection library that parses the Scala signature and can currently resolve named parameters: https://github.com/scalaj/scalaj-reflect
Unfortunately, I have not yet bound it to a Java reflection in order to be able to refer to methods, and I have not added logic to determine the default values (although this should be trivial). Both features are very high on my to-do list :)
This is not an IoC per se container, but it is a prerequisite for my other project: https://github.com/scalaj/scalaj-spring . Work on scalaj-spring stopped when it became dazzlingly clear that I could not make any worthwhile further progress until I had signature-based reflection.
PART B
All these things are for people with large enterprises. Those who have no choice but to integrate their shiny new Scala code into some kind of awkward legacy system ... If this is not your use case, then you can just make Scala DI directly inside Scala.
It supports DI support under the Lift banner: http://www.assembla.com/wiki/show/liftweb/Dependency_Injection
You should also look for links to the cake template.
source share