Reference Application Coverage Analysis

The reference application was pinned to commit 04cff95802de44d0ff5ac0802857f3bb2ffe8c3a. The probe used the current locally built 4.0.0-SNAPSHOT GraphQL artifacts and JDK 25.0.3. The source inventory covered 1,271 Java files, 276 layout XML files, 38 domain services, 351 domain-object annotations, 664 property annotations, 128 collection annotations, 612 action annotations, and 724 member-support methods.

The corresponding machine-readable artifacts are:

The matrix entry IDs are stable references used by the follow-on OpenSpec proposals.

The analysis first installed the current GraphQL reactor artifacts.

The pinned reference application contains a wicket/jpa-and-graphql directory that is not part of its normal reactor and had drifted from its current JPA application assembly. The analysis used a disposable checkout under /tmp and applied only temporary wiring changes there. Those changes aligned the child parent version, added the orphaned module to the reactor, used the JPA application as its dependency, selected ReferenceAppWicketJpa as the main class, imported CausewayModuleViewerGraphqlViewer, kept the dependency application thin, excluded Spring Boot’s default logging binding, skipped missing build information, and enabled full annotation processing for Lombok under JDK 25. None of those external-checkout changes is a Causeway production change or a reference-application dependency.

The functional server can be reproduced from the Causeway checkout root with the following commands.

The endpoint accepts the reference application’s test account through HTTP Basic authentication, for example sven:pass. The resource-policy run additionally passes --causeway.viewer.graphql.resources.response-type=DIRECT.

The authorization-sensitive probe ran first with the reference application’s Secman configuration and the GraphQL import enabled, but without the bypass dependency, module import, or analysisAuthorizorChooser from the functional patch. The broader functional probe then selected the explicit authorization-bypass implementation in the disposable checkout so that schema behavior could be distinguished from application authorization policy. The server was started with RICH_AND_SIMPLE schema style and was queried over its real HTTP /graphql endpoint.

The default resource policy and DIRECT resource policy were tested in separate server runs. Targeted one-type introspection operations were used for member details because the generated schema contains 21,142 types and broad repeated field introspection can trigger GraphQL Java’s bad-faith introspection protection.

The generated endpoint reported SimpleAndRich as the query type and Mutation as the mutation type. The rich and simple roots each exposed 430 object or service lookup fields. The mutation root exposed 3,154 fields, while logicalTypeNames__gqlv_enum exposed 277 values. The complete schema contained 20,365 object types, 732 input-object types, 33 enum types, and 12 scalar types.

This scale confirms that generic clients must use cached targeted introspection and request only the types needed for the active object context. It also makes generated type proliferation and startup cost relevant compatibility concerns for every proposed schema extension.

The current rich schema successfully covers representative domain services, concrete entities, concrete view models, mixin properties, mixin actions, dynamic hidden state, dynamic disabled state, scalar property reads, scalar property validation, action defaults, action choices, autocomplete, safe invocation, mutating invocation, and typed concrete collection rows.

The safe-versus-mutating split remained visible in the schema. Safe actions used nested query invoke fields, while state-changing actions used generated top-level mutation fields.

A scalar property validation probe returned the domain message Not of working age [18-65]. The corresponding invalid mutation was rejected as a GraphQL data-fetching error.

Action choices returned seven male and six female television characters. Autocomplete for ba returned Barbara. A representative object-list action mutation succeeded when its separate validation field was not selected.

The authorization probe reported the restricted action as hidden and did not execute it. The password parameter default was serialized as suppressed, and no clear-text password was observed.

Wicket table decorators, Wicket redirect policies, CSS implementation details, and repainting behavior are not required framework-neutral GraphQL semantics. Some source annotations may later justify optional presentation hints, but they do not justify reproducing a Wicket contract.

Domain events, command publishing, execution publishing, lifecycle callbacks, validation execution, authorization evaluation, and persistence semantics remain server-side behavior. GraphQL must enforce them during execution, but a browser component does not need a duplicate metadata model for their internal mechanics.

The pinned reference application remains external evidence and must not become a normal Causeway reactor dependency. Reduced deterministic fixtures are required for accepted behavior.

The analysis changes the provisional programme order.

The first two roadmap items are correctness or safety work and have priority P0 in the matrix. Value semantics, collection windowing, application entry points, composite rendering, and menu rendering are P1 capabilities. Independent wrapper metadata and diagnostics are P2 because effective grid and menu resources already cover much of the structural presentation vocabulary.