By: pperalta [Member]

pperalta [Member] — Fri, 09 Dec 2005 12:43:50 +0000

I suppose it depends on how your application is set up. For applications where your objects will always be singletons and their configuration never has to change, I can see where annotations can ease the maintenance burden. We use XDoclet to maintain Hibernate mappings, so we certainly see value in using annotations. So to summarize, annotations IMHO work best for places where the configuration is class wide AND it never (or rarely) has to change, especially in a production setting.

By: Terry [Visitor]

Terry [Visitor] — Fri, 09 Dec 2005 03:42:10 +0000

I’m relatively new to having an opinion on matters of Java and the related, but I wonder if those who lean against DI configuration via annotations may be overthinking the problem. I’m currently working on a project using Spring and we’ve been ‘annotating’ the hell out of our ‘services’ & DAOs via xdoclet to ease the burden of maintaining the spring config file(s). It’s working so well for us that I’m not sure I can imagine doing it any other way on such a project with multiple people all getting their hands into various files and such. I can’t understand why anyone would want to have to keep source and config files ‘in-sync’ manually. Or, taken from another perspective, what’s the downside to this approach? I understand it might not work for datastore-type objects for which there can be multiple instances (and we don’t do that anyway). But for objects that are written and intended to be singletons from the get-go, that argument doesn’t apply at all. Those are my thoughts…

Comments on: Notes on the expert panel

By: pperalta [Member]

By: Terry [Visitor]