This is what I have been thinking, and it seems to me that James is moving in this direction with his thoughts on interceptors as he is suggesting that HM will look like AspectJ, but externalised into XML. I think that sometimes it is advantageous to use annotations, but sometimes to use XML. At least in this regard that with annotations they are immiediate and the thought process of the developer is uninterupted whereas with XML there is a central repository to the "annotations" that can be inspected, thought about and modified on their own, without having to look at many different classes. Adam
On 31/07/06, devel - Fashion Content <[EMAIL PROTECTED]> wrote:
What if T5 implemented a strictly annotation based IoC container, and HiveMind supported the same annotations but also supported the current xml based configuration. What if T5 could work together with HiveMind or on it's own depending on wether you need backwards compatibility. Yes I see that it would potentially require a parallel set of annotation classes and parsing methods and some odd glue to merge the two, but wouldn't it be a neat way to achive both objects from the user perspective. Henrik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
