Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>All you need here is a cast to a raw type. As in <a href="https://stackoverflow.com/users/975497/chooks">chooks</a>'s comment below (thank you!), Guice effectively acts like a map from key (often the class object) to value (Provider of that class), and the generics just help to keep the common case sane. If you're sure that your key matches, you can override the generics like this:</p> <pre><code>@Override protected void configure() { for (Object object : getYourListOfInitializedObjects()) { bindObjectAsSingleton(object); } } /** Suppress warnings to convince the Java compiler to allow the cast. */ @SuppressWarnings({"unchecked", "rawtypes"}) private void bindObjectAsSingleton(Object object) { bind((Class) object.getClass()).toInstance(object); } </code></pre> <p>As <a href="https://stackoverflow.com/users/788207/vladimir-matveev">Vladimir</a> mentioned above, this tends not to encourage good Guice design, because even if you have your <code>DependencyImpl</code> implement <code>Dependency</code>, the above will only create a binding to <code>DependencyImpl</code>. Also, all classes in your list of initialized singletons must be created without the benefit of Guice injection themselves, so you're restricting yourself to classes you've initialized externally without Guice's help. You might use the above pattern if you're migrating from a legacy "pile of singletons" into Guice, but you'll probably get farther if you structure your <code>configure</code> method like this as soon as possible:</p> <pre><code>@Override public void configure() { // Let Guice create DependencyOne once, with injection, // immediately on injector creation. bind(DependencyOne.class).asEagerSingleton(); // Let Guice create DependencyTwo once, with injection, // but this way you can hopefully rely on interface DependencyTwo // rather than concrete implementation DependencyTwoImpl. bind(DependencyTwo.class).to(DependencyTwoImpl.class).asEagerSingleton(); // Bind DependencyThree to an instance. Instance bindings are // implicitly singletons, because you haven't told Guice how to // create another one. bind(DependencyThree.class).toInstance(getDependencyThreeInstance()); // ...and so forth for everything in your list. } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POBind Class<?> with Guice
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USJeff Bowman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBind Class<?> with Guice
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThis is a good answer. To add a little bit of value to the OP -- if you read up on how guice stores bindings internal with a Key value, then this may make it a little clearer about how to work with generics. I know that I had problems making the conceptual shift with my code (that used a lot of parameterized types/methods/etc...) and finally understanding the actual binding mechanism made things much clearer for resolving issues involving generics and the use of things like TypeLiterals.
      singulars
      1. PO
      1. USchooks
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload