Comment #19 on issue 258 by gili.tzabari: [Patch] custom annotation based injection points http://code.google.com/p/google-guice/issues/detail?id=258
"You'd then be happy with [...]"? String and URL are bad examples in that they are concrete classes but I get your point. To answer your question, I would be happy with com.ibm.ArrayList that implements java.util.List. I would choose to use java.util.List all over my code (to remain portable across implementations) but the fact that com.ibm.ArrayList shows up in my import statement is just fine. Furthermore, nothing prevents Guice from implementing standard interfaces in the future if some official JSR is published. The fact of the matter is that no such standard exists today so this discussion is moot. Look at what happened to Hibernate once JPA came out. You can still use the old Hibernate classes or the new JPA ones. You can even use the two together, they aren't mutually exclusive. Another example, Jersey as an implementation of JAX-RS. When you use Jersey you end up with both JAX-RS and Jersey import statements. There is no contradiction there. JAX-RS publishes interfaces. Jersey publishes implementation classes. -- 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 -~----------~----~----~----~------~----~------~--~---
