Bob Lee wrote:
> On Mon, Sep 14, 2009 at 8:38 PM, Gili <[email protected]
> <mailto:[email protected]>> wrote:
>
> A few months ago I asked whether one should expose Guice in public
> APIs or hide it. I was advised to use Guice under the hood (to improve
> testability) and expose factory classes to end-users. Here is what
> I've got so far:
>
>
> Do your clients not use Guice?
>
> My first suggestion would be to get them on Guice. Then, you just give
> them a Module that creates bindings to StatelessClass and StatefulClass.
>
> If that isn't possible, I'd avoid static. What's the scope/relationship
> between Stateful and StatelessClass?
>
> Bob
Hi Bob,
This is a surprising reaction because I was thinking the same thing
when I first brought this up a few months ago. I noted that very few
public APIs expose Guice (see Google's own APIs for example!) and when I
brought this up it was suggested that I hide Guice from end-users too to
reduce the learning curve.
So to bring this back full circle: why don't more APIs expose Guice to
end users?
Gili
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-guice" 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?hl=en
-~----------~----~----~----~------~----~------~--~---
