This repository powers the public GuicedEE website hosted at https://guicedee.com, presenting the entire GuicedEE ecosystem with the documentation, samples, and builder tools consumers expect.
The build publishes llms.txt, a complete llms-full.txt, individual references
for 127 Maven components, Markdown versions of all documentation routes, robots
and a sitemap. See crawler discovery for coverage,
source refresh, nginx behavior, verification commands and the live-site audit.
The homepage, builder and crawler-documentation updates are live at
guicedee.com. Revision
guicedee-website--v260-20261116-eb67f07 is healthy and serves 100% of traffic.
All 298 public assets match the verified build. Runtime target sits beside
Language, and Service Discovery is grouped under Cloud SDKs. Release highlights
from 2.6.0 through 2.4.0 use aligned, responsive card grids. The homepage selector
reads Developer, and the Native-Image comparison names GuicedEE, Quarkus and
Micronaut alongside their chart and table values. The site also serves the complete
AI reference, robots and sitemap. Page section links sit beneath their page in
the desktop menu and mobile drawer. Only one branch stays expanded, and page
navigation opens the matching branch. The right sidebar has been removed;
Modules, Services and Environment Variables retain their filters in the page.
Releases lists 15 documented versions, newest first. Capabilities nests its 23
section links within five groups: Core & configuration, Web & security, Data &
messaging, Cloud & deployment, and Observability & resilience. Only one group
stays open; section links, search and browser history reveal the matching group.
Home's Explore the platform branch includes an Overview link and all 13 platform
sections. Its links open the disclosure and reveal the selected section below
the fixed header, including when arriving from a bookmark or search result.
The 2.6.0 release highlights now include the public benchmark suite, developer
builds, native runtime and reactive persistence results. Measurements are dated
15–16 November 2026 and link to the retained benchmark revision f5770f2.
The site always uses dark mode, including the initial HTML and browser controls,
regardless of system settings or saved theme preferences. The theme toggle is
removed and the header star uses the lighter brand pink at full opacity.
Carousel scrolling continues onto the page at either end of a slide, including
slides that need no internal scrolling. Section links no longer include a fixed
750 ms pause; they wait only for the required rendering or component transitions.
Compile and JVM package now show both GuicedEE modular JAR discovery modes,
SPI and scanner, labelled java -m, alongside Quarkus and Micronaut. The chart
labels fit on mobile and match the complete build grid.
The App Builder groups its module options into two columns when space permits,
with the preview alongside on large screens and below on smaller screens. Phones
use one option column. Selections and generated project downloads work across both
columns, including nested Service Discovery options under Cloud SDKs.
Environment reference tables use compact rows and predictable column widths.
Each table has a Wrap text switch; full values also appear on hover. The tables
remain semantic HTML, with their complete text available to search and readers.
Data & persistence lists JSON, Excel and XML representations alongside Apache
Commons CSV, with actual module coordinates and individual reference documents.
The Excel summary describes worksheet-to-object reading; CSV uses the Commons
CSV service module and its upstream API.
The homepage carousel has pink previous and next arrows beside its eight dots.
The controls preserve slide width and stay synchronized with the top selectors,
including keyboard navigation and mobile layouts.
The builder preview now occupies the page aside on wide screens; module groups
start collapsed and clustering guidance appears when selected. Getting Started
includes working next-step cards, a build-tool action and a readable lifecycle graph.
The carousel also has slide-edge arrows and a native runtime results table.
Java examples use a midnight-style syntax palette. A back-to-top button appears
after scrolling, and the IntelliJ Marketplace card sits in the home-page aside.
Capabilities compares the JVM architecture with the experimental WASI probes and
describes both ClassGraph and SPI discovery.
Getting Started also uses the page aside for its Marketplace display. Introductory
banners have a bottom-centred radial glow. Capabilities includes a REST client
registry example, a darker configuration graph and responsive SDK cards.
The builder previews generated project files in a dialog using the same ZIP
contents as the download; native-image setup has its own information dialog.
Selecting a page in navigation returns to the top.
The project file tree uses compact rows. The Releases menu shows five recent
versions and a link to the next older release.
Project previews compact single-folder paths and show the selected build file.
Generated projects omit the empty application module and its service entry.
Getting Started includes a Hello World file browser and modular launch commands;
its Maven and Gradle examples returned the greeting in local runtime checks.
Home examples precede their feature cards, and lifecycle and scope descriptions
have been refined.
See the
deployment record for the source revision,
immutable image and validation details.
Revision guicedee-website--v250-20261102 served 100% of traffic before the update above.
Its image was docker.io/gedmarc/guicedee-website@sha256:0f2aa357fd405c2ba514740686577260c59329b2dc49ec033c320aa585a6f3fe.
All 94 public HTML/JavaScript/CSS assets matched that production build, and
six SPA routes returned the matching index. Release notes, catalog versions
and application examples targeted 2.5.0. The separate backend was not redeployed.
Evidence: target/release-2.5.0-website-public-verification.json in DevSuite.
The version badge, module and service catalogs, dependency examples, and Maven/Gradle application downloads target GuicedEE 2.4.2. The release page covers the refreshed reactive runtime, official Swagger Core 3 integration (including its pinned upstream snapshot), and Maven 4 model 4.1.0. Historical release notes and deployment records remain dated to the versions they describe. Regenerate the Angular site from its Java sources using the commands below before deployment.
The capabilities page documents explicit cluster activation, lifecycle ownership, separate member/event-bus endpoints,
owner-local STOMP commands, private replies/storage, broadcast fan-out, bounded socket cleanup and reconnect recovery.
The environment reference includes the activation gates and Hazelcast member settings. The application builder uses
com.guicedee:hazelcast / com.guicedee.guicedhazelcast and com.guicedee:websockets / com.guicedee.vertx.sockets.
The release changelog describes the production capabilities shipped with GuicedEE.
The Application Builder offers separate Hazelcast (cache-only) and Vert.x clustering (Hazelcast)
selections. Either adds the Hazelcast dependency and a cluster/package-info.java preview and source file.
Clustering generates explicit TCP membership and advertised event-bus endpoints, plus cluster-a.env.example,
cluster-b.env.example, single-instance.env.example, and CLUSTERING.md in both Maven and Gradle downloads.
Load the environment examples explicitly into separate processes; they are not automatically read.
The generated Boot uses GuiceApplication.run(Runnable) and enables scanning in its preparation callback.
Generated Maven projects pin Compiler Plugin 3.15.0 for Java 25 bytecode support. The GuicedEE BOM manages
the current com.guicedee:hazelcast coordinate so clustering selections need no dependency version override.
Regenerate from Java and build the production front end locally, without creating a Docker image:
# From GuicedEE/website with the required JDK 25 selected:
mvn.cmd -B -ntp install '-Djwebmp.angular.docker=false' '-Dmaven.javadoc.skip=true'
Push-Location target/webroot/guicedee-website
npm.cmd run build-prod
Pop-LocationCheck the regenerated production bundle and its new section/aside anchors; Maven success alone does not prove fresh browser output. Keep generated TypeScript untouched and fix its Java owners. Publishing or deploying is separate.
- Surface every GuicedEE module and plugin alongside its capabilities so users can discover, inspect, and compose the platform into new apps.
- Provide a dedicated Services directory that highlights each modular service offering and explains how it plugs into the larger GuicedEE stack.
- Offer an Application Builder UI that lets visitors choose GuicedEE modules/plugins, configure settings, and download a ready-to-run ZIP containing the generated source package tailored to their selections.
- Treat GuicedVertx and GuicedInject as implicit foundations for every construction flow; they are assumed by default whenever GuicedEE modules are composed.
- Show a single monolithic application entry point using
GuiceApplication.run(Runnable)fromcom.guicedee.guicedinjection. Register the application's JPMS module in the preparation callback before injection. The runner waits for asynchronous startup; failures trigger cleanup and an unsuccessful process exit. - Document hosting/security expectations: the site runs on Azure Container Apps behind the platform's managed ingress (TLS termination + Azure edge protection) and remains otherwise open to the public.
- Curate extensive media-rich write-ups and imagery for each module, service, and plugin, enabling the marketing/evangelism story to come alive alongside the data and application builder.
- Generate every page with the JWebMP/WebAwesome stack so that the WebAwesome components (
WaButton,WaInput,WaCluster,WaStack, etc.) drive the layout, styling, and interactive media galleries. - Define the primary navigation and page structure using WebAwesome’s
WaPage/WaMenuparadigms: aHomepage that narrates the platform story, aCapabilitiespage for features breakdown, aServicescatalog page, the App Builder page, and supporting destinations for releases, media, and onboarding resources.
cdi(migration and compatibility — not a foundation module)cerialclientconfiginjectopenapipersistencerabbitmqrepresentationsrestswagger-uitelemetryvertxwebwebserviceswebsockets- (catalog is a curated static list defined in
ModuleCatalog; it intentionally excludes non-modular directories likebom,parent,services, and thewebsiteitself)
Each catalog entry links to its documentation, release notes, and live demos wherever available.
Note: This section describes the technology used to build and run this website itself (not the output of the Application Builder).
- Website UI: TypeScript front end using JWebMP foundations, WebAwesome, and WebAwesome Pro with component names
WaButton,WaInput,WaCluster, andWaStack(seeGUIDES.md). - Java 25 + Maven backend powered through the
GuicedEE/parentBOM chain and theguice-inject-clientdependency; logging via Log4j2 with Lombok@Log4j2helpers. - MapStruct for DTO-to-model transformations, Mermaid for diagrams (served from
docs/architecture/via Mermaid MCP), and CRTP-based fluent APIs across shared modules.
This site’s Services section lists a complete, statically-defined set of modularized services (no filesystem scanning at runtime), currently covering:
- Apache Commons:
commons-beanutils,commons-collections,commons-csv,commons-fileupload,commons-math - Apache CXF (Web Services):
apache-cxf,apache-cxf-rt-security,apache-cxf-rt-transports-http - Apache POI:
apache-poi,apache-poi-ooxml - Database Drivers:
msal4j,mssql-jdbc,postgresql - Google:
aop,guice-core,guice-assistedinject,guice-grapher,guice-jmx,guice-jndi - Hibernate:
hibernate-core,hibernate-reactive,hibernate-validator - JCache:
cache-annotations-ri-common,cache-annotations-ri-guice,cache-api,ehcache,hazelcast,hazelcast-hibernate - JNI:
jna-platform,nrjavaserial - Jakarta:
jakarta-security-jacc - Libraries:
bcrypt,cloudevents,ibm-mq,jandex,javassist,json,kafka-client,mapstruct,openpdf,rabbitmq-client,scram,swagger,testcontainers,uadetector-core,uadetector-resources - MicroProfile:
config-core,metrics-core - Vert.x:
vertx-cassandra,vertx-mutiny,vertx-kafka,vertx-pg-client,vertx-rabbitmq - Misc:
untitled
Each service card describes configuration patterns, integration requirements, and the modular contracts they expose so teams can adopt them independently.
Note on scope: The Application Builder is for composing GuicedEE modules and services. JWebMP/WebAwesome are the technologies used to power this website and the optional UI starter in the generated ZIP, but they are not selectable modules in the builder and the builder is not a JWebMP project generator.
Visitors can craft a custom GuicedEE application by:
- Selecting desired GuicedEE modules and plugins from the Module Catalog.
- Picking the services they wish to include from the Services Section.
- Configuring optional settings (e.g., logging level, MapStruct mapping mode, service configuration presets).
- Clicking Build App to trigger the builder backend which packages the chosen artifacts into a ZIP archive containing:
- Maven parent/child POM structure wired for Java 25/GuicedVertx/Inject.
- Optional minimal UI starter scaffold (if explicitly selected); by default, no Angular or JWebMP code is generated by the builder.
- A monolithic
Bootclass that callsGuiceApplication.run(Runnable)to spin up the composition, using the module name frommodule-info.javain its preparation callback. - Service-specific wiring snippets that show how to bootstrap each modularized service.
The generated ZIP mirrors production builds so teams can iterate quickly without configuring every dependency manually.
The public site is a static Angular SPA served by nginx — the angular-maven-plugin emits the Angular project to target/webroot/guicedee-website, ng build writes dist/jwebmp/browser, and the generated Dockerfile copies that into an nginx:alpine image. Dynamic data comes from the separate website-backend deliverable, not from this container.
Runtime topology
| Setting | Value |
|---|---|
| Platform | Azure Container Apps |
| Container app | guicedee-website |
| Resource group / region | DevSites / UK West |
| Image | docker.io/gedmarc/guicedee-website:<version> (public Docker Hub, anonymous pull) |
| Ingress | External, target port 80, transport Auto |
| Custom domain | guicedee.com via Azure managed certificate (SNI) |
| Revisions | Single mode, traffic pinned to latestRevision at 100% |
| Scale | min 0 / max 1, HTTP scaler at 10 concurrent requests |
| Resources | 0.25 vCPU / 0.5 GiB, Consumption workload profile |
| Probes | TCP :80 liveness, readiness, and startup |
Because
minReplicasis0, the app scales to zero when idle — the first request after a quiet period pays a cold start.
Deploying a new version
Deployment verified on 16 October 2026: revision guicedee-website--v241-20261016
serves 100% of traffic from docker.io/gedmarc/guicedee-website@sha256:5a59bea733666fa5472a9fe3b33c514cb8a2d4b6ec3fd849ce3f106f11dcf316
(tag 2.4.1-20261016). All 94 HTML/JavaScript/CSS assets and six public routes
match the local production build. The catalog, examples, application downloads and
release notes target GuicedEE 2.4.1. The website backend was also upgraded to revision
website-backend--v241-20261016; readiness, APIs, CORS and protected internal routes passed.
Previous deployment, verified on 15 October 2026: revision guicedee-website--v240-apm-20261015
serves 100% of traffic from image
docker.io/gedmarc/guicedee-website@sha256:ac058aecc740e83bfe2969bdc83987ecdcb2bbc81ffa08dc9ad83f825652b8df
(tag 2.4.0-20261015-apm). The homepage and main JavaScript
bundle match the local production output. The deployment includes the IntelliJ
plugin section, APM marketplace/installer instructions directly below it and simplified three-layer
architecture diagram. The backend is unchanged.
-
Build and push the image (see
build-guicedee-website.ps1 -Push, ormvn installthendocker build/docker pushfromtarget/webroot/guicedee-website). Keep<dockerImageName>inpom.xmlin step with the release. Use subscriptionaee3c089-49a8-472c-8d40-5bf568a1ff55(Pay-As-You-Go), tenant58d3b009-4fc6-44c1-bc98-197165d3fd04, explicitly. Do not rely on the Azure CLI default subscription. -
Point the container app at the immutable image digest. Because revisions run in
Singlemode withlatestRevision: true, the new revision automatically takes 100% of traffic — no manual traffic split:az containerapp update ` --subscription aee3c089-49a8-472c-8d40-5bf568a1ff55 ` --name guicedee-website ` --resource-group DevSites ` --image docker.io/gedmarc/guicedee-website@sha256:5a59bea733666fa5472a9fe3b33c514cb8a2d4b6ec3fd849ce3f106f11dcf316 ` --revision-suffix v241-20261016
Without the
containerappCLI extension, an ARMPATCHagainstproperties.template.containers[0].imageachieves the same result. If you hand-roll the payload, re-send the probes, resources, and scale rule as well — atemplatepatch replaces the containers array. Note that the read API returnsscale.cooldownPeriodandscale.pollingInterval, but api-version2024-03-01rejects those two on write; omit them and the existing values are retained. -
Verify:
provisioningStateisSucceeded,latestReadyRevisionNamematches the new suffix, andhttps://guicedee.com/returns the freshly builtindex.html(comparecontent-length/last-modifiedagainstdist/jwebmp/browser/index.html). Confirm the SPA fallback still serves deep links such as/releasesand/modules.
Security
- TLS terminates at the Azure Container Apps managed ingress using the Azure managed certificate; no application-level firewalling is applied today.
- CI harness uses GuicedEE/Workflows shared GitHub Actions templates with secrets such as
USERNAME,USER_TOKEN,SONA_USERNAME,SONA_PASSWORD.
- Run
mvn -B -U verifyto build the website;docs/architecture/anddocs/PROMPT_REFERENCE.mdlink all stage-gated artifacts. - Stage 1–3 docs (PACT/RULES/GLOSSARY/GUIDES/IMPLEMENTATION) are required before any Stage 4 scaffolding touches actual Angular or Java sources.
- See
.env.examplefor environment variables aligned withrules/generative/platform/secrets-config/env-variables.md. - Architecture diagrams (C4, sequences, ERD) live under
docs/architecture/; Mermaid sources are served via Mermaid MCP (https://mcp.mermaidchart.com/mcp).
- AI Skills:
SKILLS.md - Prompt reference:
docs/PROMPT_REFERENCE.md - Architecture index:
docs/architecture/README.md
- Keep the documentation loop closed: PACT ↔ RULES ↔ GUIDES ↔ IMPLEMENTATION ↔ GLOSSARY.
- Apply forward-only changes and honor the Document Modularity Policy outlined in
rules/RULES.md.
- Apache 2.0 — see
LICENSE.
The Releases and Capabilities pages preview the modular Firebase/Commercetools SDKs, external modular dependencies, Jackson 3 policy for Commercetools, SDK Javadocs and full application jlink validation. See the release notes. Website examples and version badges target 2.6.0. Publication and deployment remain pending.
The final carousel item introduces WebAssembly · Experimental and links to
the indexed WebAssembly heading on /capabilities. The detail section distinguishes the verified standalone
Guice and outbound HTTP probes from the planned typed REST-client/Jackson 3 and JWebMP
rendering work. It includes a dated validation snapshot and is indexed by site search.
This content is prepared locally; it does not announce a supported Wasm release or a deployment.
The App Builder offers independent Firebase Admin and Commercetools SDK selections with BOM-managed wrapper coordinates and their original JPMS names. Services lists both SDKs and the Zstd/Okio support modules. The runtime selector defaults to a JVM JAR; Native image starter adds explicit SPI discovery, reflection registration, dual service registration, NativeBuild.java and NATIVE.md to Maven and Gradle ZIPs. Build previews use the same content as downloads. GraalVM compilation and workload-specific metadata remain application validation steps; selecting an SDK does not assert native compatibility for all its products.
The generated Maven starter with both SDKs selected passed a Linux native build and startup check after adding baseline Guice reflection metadata to both generators. See the native starter validation report for the exact scope, environment and evidence. A separate copy with the benchmark workload and its native compatibility setup also passed actual Commercetools OAuth/REST/GraphQL and Firebase Firestore write/read calls on JVM and native, using the benchmark's local fixtures. See the SDK operation validation report for assertions, fresh metadata, reproduction commands and results.
Quarkus is the primary comparison because both frameworks build on Vert.x, as described in Quarkus's reactive architecture. The shared reactive foundation and stack example make the comparison useful; injection, configuration and application models still differ. The Performance slide explains this choice, with implementation details in the CDI slide.
The homepage uses a manual Web Awesome carousel and Pro wa-chart bar charts. The long platform tour is retained in an expandable section. Numeric summaries accompany each chart for accessibility; axes start at zero and animation is disabled.
BenchmarkShowcase fetches these public files once per page visit (8-second timeout, independent failure handling):
https://raw.githubusercontent.com/GuicedEE/benchmarks/master/docs/current-performance.json:native-standardstartup and peak container memory, with measurement date and sample counts.https://raw.githubusercontent.com/GuicedEE/benchmarks/master/docs/build-performance.csv: clean JVM compilation forguicedeeandquarkus-standard.https://raw.githubusercontent.com/GuicedEE/benchmarks/master/docs/persistence-performance.json: default-profile startup through the first committed graph, joined-read p50 and CRUD-cycle p50.
Startup, memory and build charts retain a labelled 15 November 2026 public snapshot if fetching or validation fails. Persistence retains the validated 16 November 2026 snapshot, with separate startup, read and CRUD-cycle views. Finite positive numeric values are required. Source text is Angular-interpolated, never injected as HTML. The full report links retain methodology and raw evidence. These are separate benchmark cohorts, not universal framework performance claims. Snapshot refresh and browser verification describes the publication contract.
The comparison cards use compact wa-data-grid rows beneath each chart. Developer builds default to clean compile versus clean compile, with separate JVM packaging and native-build views. Each chart shows its matching pair: GuicedEE SPI and Quarkus fast-JAR for compile/JVM package; GuicedEE native and Quarkus native for native build. Methodology stays in the linked benchmark report. Native runtime panels compare GuicedEE native with Quarkus native. Application jlink remains covered by the detailed benchmark report, outside the homepage comparisons.
The native build comparison validates the published CSV baseline (quarkus-standard-native) before accepting refreshed data. All homepage comparisons retain the public-data and dated-fallback policy above.
The developer-build panel retains the complete nine-artifact build grid from RESULTS.md, including Micronaut JVM/native: compile/package medians, both min–max ranges, explicit baseline and package difference. It spans the panel below the chart and stays visible across chart modes. All nine rows refresh atomically from the published CSV; incomplete rows, invalid ranges or unexpected baselines retain the dated snapshot.
The startup panel includes a nine-row runtime grid: stack-example startup median/range, starts, warm p50, peak charged container memory, matching baseline and startup percentage difference. Default/C1 switches the six JVM rows, while the three separately measured native rows remain unchanged. The table uses the same public summary JSON as the native chart, with validated complete cohorts and dated snapshots.
The Kotlin carousel slide presents the planned launch support across GuicedEE modules, with constructor injection, coroutine work and Kotlin data classes. Its example follows the current GuicedCoroutines.future boundary and links to the Kotlin examples. The module-wide Kotlin work is still in progress; this website copy is staged for its completion before launch.
Search sits above Home in the left menu, aligned with the homepage carousel selectors, and also appears in the mobile drawer. A theme-colored magnifying glass prefixes the field; results float in an anchored WebAwesome popup without moving the navigation. Its local index is generated from the page component trees, including module/service descriptions, static examples and environment-variable tables. Results show their page, section and an excerpt around the match. Opening a result navigates to a stable heading fragment, expands enclosing details or selects its carousel slide, then scrolls to and highlights the heading. Result URLs also work on reload and browser back/forward, with the matching aside preserved. Remote README dialogs and builder options that require changing selections are excluded. Keyboard users can press Enter for the first result, use arrow keys through results, or Escape to dismiss them; clicking outside also closes the popup.
After building, run node tools/verify-site-search.cjs with Playwright available (or set PLAYWRIGHT_MODULE to its installed module path). It checks cross-page results, carousel/disclosure reveal, fragments, snippets, keyboard controls, no-match/clear states and the mobile drawer. Search does not send queries to an external service.
The CDI panel records the local benchmarks/docs/CDI-CONFIG-VALIDATION.md evidence from 15 November 2026 (five CDI variants, 16/16 checks each). It explicitly distinguishes capability validation from performance rankings; public performance JSON currently contains no CDI rows. Expandable excerpts show the actual Jakarta annotations, packaged application.properties, environment overrides, bootstrap and JPMS setup, including the different Quarkus configuration/initialization pattern. Native is SPI-only.
Artifact cells in the build/runtime grids use decorative wa-progress-bar backgrounds via the Web Awesome cell formatter API. Bar length is the absolute package/startup percentage difference, capped at 100%; the signed value remains in its own column. Baselines use a neutral background. The progress component is preloaded for the grid shadow DOM, and artifact labels are inserted as text rather than HTML.
The Application Builder includes a Java / Kotlin language selector. Kotlin downloads contain Boot.kt,
AppModule.kt, a JUnit test, Kotlin 2.4.21 Maven/Gradle configuration, and the GuicedEE Kotlin runtime.
Previews and ZIP downloads use the same language selection. JPMS descriptors, package annotations and
native-image registration/build helpers remain Java in the mixed-source project.
Local validation covers the production Angular builder, browser-downloaded Maven and Gradle ZIPs, and
real JVM builds/tests, including Firebase and Commercetools with native starter selected. It does not
claim a Kotlin native-image executable or live cloud-service calls. Nothing is deployed by these checks.
Run tools/verify-kotlin-builder.cjs with PLAYWRIGHT_MODULE pointing to your Playwright installation,
then Maven 4 verify / Gradle 9.4.1 build in target/kotlin-generated using JDK 25.
Unpublished 2.6.0 artifacts must be installed locally; Gradle validation uses a local-repository init script.