Re: empty interfaces via reflection
Arne VajhQj wrote:
I still can not really see any reason why not to use AspectJ.
Yes - you need to distribute the aspectrt.jar, but most Java apps
require some jars.
Yes - developers will need the AspectJ tools, but they also need
an editor, a Java compiler etc..
Be careful which version of AspectJ you use. Apparently some older versions
had trouble in multi-threaded, multi-processor environments. I have heard
that these troubles were repaired in the latest release(s).
It is also true that AspectJ defines a superset language to Java, which may be
the OP's concern with it. They do take care to maintain complete binary
compatibility with "plain" Java, though.
Still, I don't think you should minimize the differences from "plain ol' Java"
that AspectJ does introduce to the language. Perhaps they are worthwhile, but
the OP is correct to investigate the impact of these differences.
Disclaimer: I am not anything but superficially familiar with AspectJ,
although I did review their documentation as I wrote this post.
--
Lew