Comment #16 on issue 70 by robbie.vanbrabant: Support any annotation in place of @Inject http://code.google.com/p/google-guice/issues/detail?id=70
To answer @mcculls' question: http://java.sun.com/javase/6/docs/api/javax/annotation/Resource.html It would still mean "inject here!" but all the attributes on it would not work. It would probably even be confusing to have attributes set that Guice simply ignores. That's what I meant with framework portability, right? Seriously, if you have to write portable code with _any_ DI framework, you have to be very careful. You would have to stick to the bare minimum, which is why people don't switch frameworks on existing code. Ever used Spring's container lifecycle, FactoryBean, ... Guice's Provider, .. ? It's like database portability. It's nice to be portable, but you have to be realistic. Your company runs on Oracle? For God's sake, use those Oracle-specific features and get it over with. :) But indeed, let's stick to "anything named @Inject" and/or support for @Resource. Maybe change the issue title? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en -~----------~----~----~----~------~----~------~--~---
