1. Domino Brix
2. Presenter lifecycle
3. Activation & authorization

activate()

Activation starts when the route matches. Brix checks authorization, registers listeners, marks the presenter active, and attempts to reveal the view.

• Authorization: getAuthorizer().isAuthorized(...); unauthorized calls reportUnAuthorizedAccess().
• Listeners: slot listener (for reveal), event listener (for @ListenFor), navigation interceptor if the view confirms navigation.
• Active flag: onActivated() fires, then auto-reveal runs if enabled.

Authorizers

Use built-ins or custom authorizers to control access.

			@BrixPresenter
@BrixRoute("dashboard")
@BrixSlot(BrixSlots.BRIX_BODY_SLOT)
public class DashboardPresenter extends Presenter<DashboardView> {
  // No manual view binding needed
}

@UiView
public class DashboardView extends BrixView<Element, DashboardHandlers>
    implements DashboardPresenter.DashboardView {
  @Handlers DashboardHandlers handlers;
}

		

Branches

• Slot not registered yet: activation completes, reveal waits until onSlotRegistered.
• Child presenter: may defer until parent is active.
• Disable activation entirely by overriding isEnabled() and returning false.