StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6974667
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-07T18:03:10.813
FavoriteCount
0
LastActivityDate
2011-08-07T18:03:10.813
LastEditDate
LastEditorUserId
0
OwnerUserId
533873
ParentId
6968474
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Using <a href="http://code.google.com/p/google-guice/wiki/Multibindings" rel="nofollow">MapBinder</a> extension you can get injected with several bindings contained in a <code>Map</code>. Then it's a matter of implementation which one to use. You will need a key, in your case that could be a <code>String</code> or <code>Enumeration</code> and bind all <code>Payment</code> implementations to the appropriate keys: <pre><code>public class MyModule extends AbstractModule { @Override protected void configure() { // this one aggregates all bindings and could be further annotated if you // need several maps with same key/value types MapBinder<String, Payment> mapBinder = MapBinder.newMapBinder(binder(), String.class, Payment.class); // simple binding of PaymentCashImpl to 'cash' key mapBinder.addBinding("cash").to(PaymentCashImpl.class); // you can scope during binding or using @Singleton annotation on implementations mapBinder.addBinding("card").to(PaymentCardImpl.class).in(Singleton.class); } } </code></pre> Then in <code>Order</code> you get injected with the whole map and decide which implementation to use: <pre><code>public class Order { @Inject Map<String, Provider<Payment>> paymentProcessors; public void finishOrder(String paymentMethod) { if (!paymentProcessors.containsKey(paymentMethod)) { throw new IllegalArgumentException("Unknown payment method " + paymentMethod); } Payment paymentProcessor = paymentProcessors.get(paymentMethod).get(); // do your stuff... paymentProcessor.pay(); } } </code></pre> Note: Injecting providers doesn't work with <code>javax.inject.Provider</code>, you need to use <code>com.google.inject.Provider</code>. By injecting providers instead of instances you can achieve lazy instantiation and different instantiation policies per implementation. Like in the example above the <code>PaymentCardImpl</code> is singleton, while the other is created each time. You can use guice <a href="http://code.google.com/p/google-guice/wiki/Scopes" rel="nofollow">scopes</a> to control the lifespan, or even implement your own provider to accomplish something else.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODependency Injection based on a condition
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGeno Roupsky
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.