RemoteSmokeTestHelperModule

Through Context Factory, the glue code has access to all of the interfaces in the context APIs. But, Context Factory alone does not have information on which impl implements a given interface.

The glue code identifies which impl to use for a given interface through a series of binders. These binders are declared in RemoteSmokeTestHelperModule.

For example, the following line of code binds the AdminContext interface to the AdminContextImpl impl. If any code references a method from the AdminContextInterface, the glue code will look in AdminContextImpl to find the implementation of the method.

// Admin Context binder
bind(AdminContext).to(AdminContextImpl)

Furthermore, some scenarios are LOB-specific. In these cases, there could be multiple impls that declare a method with the same name, but each impl has an LOB-specific implementation of the method. For these situations, RemoteSmokeTestHelperModule uses a map binder that binds every policy type to the appropriate impl.

For example, the following lines of code create a map binder for Quick Quote submissions. Each of the policy types (PERSONALAUTO and WORKERS_COMPENSATION) is mapped to an LOB-specific impl (PASubmissionContextQuickQuoteImpl and WCSubmissionContextQuickQuoteImpl, respectively).

// Quick Quote Submission Contexts
var quickQuoteSubmissionContexts = MapBinder.newMapBinder(binder(), ProductCode, SubmissionContext, Names.named("QuickQuote"))
quickQuoteSubmissionContexts.addBinding(ProductCode.PERSONAL_AUTO).to(PASubmissionContextQuickQuoteImpl)
quickQuoteSubmissionContexts.addBinding(ProductCode.WORKERS_COMPENSATION).to(WCSubmissionContextQuickQuoteImpl)