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.
Maybe i didn't use it properly... but my understanding was that the
annotation should be put on the field to be injected, and that field
belongs to my POJO (having the field injected in another class wouldn't
be quite as useful). On the other hand DM allows me to programatically
inject the field into the POJO without any API.
Anyways, I totally agree, it's just a matter of sharing opinions and if
iPOJO can serve as a wrapper for various "best practices", this alone
answers my question about its benefits.
No offense intended :)
Arjun
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
