#2857: AdminPage.java

The central administration page accessible only to users with admin privileges. Provides system-level operations grouped into five menu categories: Configuration (re-read config XML, export config, export 2FA settings), Caches (refresh all caches), Database Actions (update user preferences, create missing indices, dump database, schema export, optimize address images), System Check (integrity verification), and Development (i18n key validation, UserGroupCache debug, Hibernate Search reindexing, test data generation, system alerts). The Development menu is only visible when SystemStatus.isDevelopmentMode() is true.

Extends AbstractStandardFormPage and implements ISelectCallerPage (for calendar-based date selection). The page uses ProjectForge's content menu pattern: each action group is a ContentMenuEntryPanel with sub-menu entries, each containing a Wicket Link whose onClick() delegates to a private method.

The page also contains an AdminForm component (the body of the page) which provides additional UI elements like the system info panel, update checker, and log viewer.

Static endpoint injection via set(IProjectForgeEndpoints) — not constructor injection but a static setter. This is a legacy pattern: the projectForgeEndpoints field provides access to system info (version, build date, memory stats) that is displayed on the admin form. The static setter is called by the Wicket application initializer.

The page overrides onBeforeRender() to call checkAccess() — a method inherited from AbstractStandardFormPage that verifies the current user has the ADMIN role. If not, the user is redirected to an access-denied page. This is the only authorization check — there is no fine-grained per-action authorization; any admin can perform any operation on this page.

The Development menu has an additional guard: if (SystemStatus.isDevelopmentMode() == false) return; at the end of addDevelopmentMenu(). This means development actions are not just hidden — their menu entries are never added to the page at all when not in dev mode.

Content Menu Pattern: Instead of a flat list of buttons, the admin page uses a hierarchical menu structure. Each group (ContentMenuEntryPanel) contains sub-menu entries, each with a Wicket Link. This allows organizing 20+ admin actions into logical categories without overwhelming the user.

Anonymous inner class Links: Each action is a new Link<Void>() { onClick() { ... } } — anonymous inner classes that delegate to private methods. This is standard Wicket pre-Java-8 style. A modern rewrite would use lambda expressions (Link<Void> link = new Link<>(id) { ... } can't be a lambda because Link is a class, not a functional interface).

Static endpoint injection: projectForgeEndpoints is a static field set via a static setter. This is unusual in a Spring-managed application and exists because AdminPage is a Wicket page (not a Spring bean) and needs access to system-level information that's normally provided by Spring services. The static setter is called from the Wicket application init.