Arjun Panday wrote:
As for iPojo (I know I won't be making new friends with this..), although i've tried to use it, i haven't quite understood its true benefits: - the xml syntax has the usual drawbacks (no compilation error: so we spend ages debugging typos) - and annotations are just another form of API that all my classes end up depending upon.. also the description of my service bindings is spread out everywhere in the code instead of being clearly gathered in an xml (like SCR) or a piece of code (like DependencyManager)
Well, we are all free to our own opinion, but I cannot say your second opinion makes that much sense. If you use DM API, then your code is dependent on that API as well. If you might argue that you could centralize all of your DM API to one area, well, the same could be true for all of your iPOJO annotations too. So, I agree that annotations are just API, but it should be no worse to have a dependency on that than DM API.
Regardless, in iPOJO we try to be somewhat agnostic to this debate. Which is why we have three different approaches, XML, manifest syntax, and annotations. We have also want to mirror the DM API as well so that we can eventually merge DM and iPOJO.
-> richard
Arjun (please don't beat me!) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
