Hi Marcel,
Thanks a lot for your feedback.
I agree with you that the interface should be improved.. maybe using
different shapes for bundles, components and dependencies. For now it's
essentially the arrow pointing to what's missing.
As for Scala; I originally wrote a Java implementation of this, but it's
over 3 times longer and therefore not necessarily easier to figure out.
Scala does take a little bit of getting used to, but in my experience,
especially when it comes to filtering lists and maps, i find that
functional programming really is the way to go.
Regards,
Arjun
On 09/23/2011 03:56 PM, Marcel Offermans wrote:
Hello Arjun,
On Sep 22, 2011, at 10:42 PM, Arjun Panday (JIRA) wrote:
A Service Diagnostics service and graphical WebConsole plugin
I very much like the idea of doing diagnostics about (service) dependencies over bundles
and across "dependency management" frameworks, hunting for root causes of why
things don't come up. I briefly played with your implementation and the graphical plugin
for WebConsole.
To be honest, I did not find the graphical representation immediately obvious.
for example, it's hard to distinguish between components and services, to see
if something is a required dependency or not, etc. However, with a bit of extra
work, I think that can easily be improved.
About the implementation, I'm not the biggest fan of Scala. I can read it if I
really apply myself, but if I had to maintain this code, I would rewrite it in
Java.
That being said, I think this is something very useful and I would like to
adopt it (and I'm especially interested in what my fellow committers,
especially the ones maintaining Declarative Services and iPOJO, think about
this).
Thanks for sharing this with us!
Greetings, Marcel
