Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can do DI using Context interfaces. It is not hard, and fairly straight forward.</p> <p>A Context interface is a class that exposes all the bindings from the guice module configuration. </p> <p>This is an example of this where I'm assuming that AppPresenter+DashboardPresenter is in one package and needs one "context", while GadgetPresenter and GadgetConfigPresenter is in another package and needs another "context". The number of contexts, and how to handle them is entirely up to the user.</p> <pre><code>/** * The dependencies that need to be injected for package1 */ public interface SomePackageContext { GadgetPresenter getGadgetPresenter(); GadgetConfigPresenter getGadgetConfigPresenter(); } /** * The dependencies that need to be injected for package2 */ public interface OtherPackageContext { // These methods can take arguments.. AppPresenter getAppPresenter(Args..); DashboardPresenter getDashboardPresenter(Args..); } /** * All of the DI needed in our project. * * &lt;p&gt;We don't need the two interfaces above, we can put * everything in this interface if we have a small * project where layering is not a big issue. */ public interface PresenterContext extends SomePackageContext, OtherPackageContext { } public class MockPresenterContext implements PresenterContext { ... } public class RealPresenterContext implements PresenterContext { // This is similar to bind(...) in guice public AppPresenter getAppPresenter(Args..) { return new AppPresenter(this, otherargs...); } public DashboardPresenter getDashboardPresenter(Args..) { return new DashboardPresenter(this, otherargs...); } public GadgetPresenter getGadgetPresenter() { return new GadgetPresenter(this); } public GadgetConfigPresenter getGadgetConfigPresenter() { return new GadgetConfigPresenter(); } } public class DashboardPresenter { // @Inject private final GadgetPresenter gadgetPresenter; /* * We inject everything using the SomePackageContext. */ public DashboardPresenter(SomePackageContext ctxt) { this.gadgetPresenter = ctxt.getGadgetPresenter(); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to do manual DI with deep object graphs and many dependencies properly
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USuser239558
    1. USuser239558
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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.

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