@Brian: I agree, after thinking a little bit more about that problem and taking your comments into account I think that deferred binding might not be really suitable for my use case.
I also agree that the best approach is to set the datasource in the constructor thus enabling users to use Dependency injection if they want. But do I have to annotate the constructor with "@Inject" in order to allow for DI ? (because in that case I would create a dependency to gin and guice in my standalone library which i want to avoid). -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
