Sync documentation of main branch

Author: actions-user

_generated-doc/main/infra/quarkus-all-build-items.adoc

@@ -710,10 +710,6 @@ _No Javadoc found_
 
 _No Javadoc found_
 
-`java.util.Map<String,String> configs` 
-
-_No Javadoc found_
-
 `java.util.function.Supplier<Map<String,String>> lazyConfigs` 
 
 _No Javadoc found_
@@ -773,6 +769,17 @@ _No Javadoc found_
 
 
 
+a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/builditem/DevServicesCustomizerBuildItem.java[`io.quarkus.deployment.builditem.DevServicesCustomizerBuildItem`, window="_blank"]
+[.description]
+--
+_No Javadoc found_
+-- a|`java.util.function.BiFunction<DevServicesResultBuildItem,Startable,Startable> customizer` 
+
+_No Javadoc found_
+
+
+
+
 a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/builditem/DevServicesLauncherConfigResultBuildItem.java[`io.quarkus.deployment.builditem.DevServicesLauncherConfigResultBuildItem`, window="_blank"]
 [.description]
 --
@@ -798,12 +805,9 @@ _No Javadoc found_
 a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/builditem/DevServicesRegistryBuildItem.java[`io.quarkus.deployment.builditem.DevServicesRegistryBuildItem`, window="_blank"]
 [.description]
 --
-_No Javadoc found_
--- a|`io.quarkus.devservices.crossclassloader.runtime.RunningDevServicesRegistry tracker` 
-
-_No Javadoc found_
-
-`java.util.UUID uuid` 
+This is a wrapper around the RunningDevServicesRegistry, so the registry can be loaded with the system classloader The QuarkusClassLoader takes care of loading the tracker with the right classloader 
+This build item is used to manage the lifecycle of dev services across different features and launch modes.
+-- a|`java.util.UUID uuid` 
 
 _No Javadoc found_
 
@@ -821,28 +825,47 @@ _No Javadoc found_
 a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/builditem/DevServicesResultBuildItem.java[`io.quarkus.deployment.builditem.DevServicesResultBuildItem`, window="_blank"]
 [.description]
 --
-BuildItem for running dev services. Combines injected configs to the application with container id (if it exists). 
+BuildItem for discovered (running) or to be started dev services. 
 Processors are expected to return this build item not only when the dev service first starts, but also if a running dev service already exists. 
-`RunningDevService` helps to manage the lifecycle of the running dev service.
+Two builders are provided to create this build item: 
+- `DevServicesResultBuildItem#discovered()` for discovered dev services, provides config to be injected to the application with container id (if it exists). 
+- `DevServicesResultBuildItem#owned()` for owned dev services, that will be started before application start, provides the startable supplier and config injected to the application and post-start action. 
+`RunningDevService` is deprecated in favor of builder flavors.
 -- a|`java.lang.String name` 
 
-_No Javadoc found_
+The name of the dev service, usually feature name.
 
 `java.lang.String description` 
 
-_No Javadoc found_
+A description of the dev service, usually feature name with additional information.
 
 `java.lang.String containerId` 
 
-_No Javadoc found_
+The container id of the dev service, if it is running in a container. If the dev service is not running in a container, this will be null.
 
 `java.util.Map<String,String> config` 
 
-_No Javadoc found_
+The map of static application config
 
-`io.quarkus.deployment.builditem.RunnableDevService runnableDevService` 
+`java.lang.String serviceName` 
 
-_No Javadoc found_
+If the feature provides multiple dev services, this is the name of the service
+
+`java.lang.Object serviceConfig` 
+
+The config object that is used to identify the dev service
+
+`java.util.function.Supplier<Startable> startableSupplier` 
+
+Supplier of a startable dev service
+
+`java.util.function.Consumer<Startable> postStartAction` 
+
+An action to perform after the dev service has started.
+
+`java.util.Map<String,Function<Startable,String>> applicationConfigProvider` 
+
+A map of application config that is dependent on the started service
 
 
 
@@ -9163,6 +9186,10 @@ _No Javadoc found_
 
 _No Javadoc found_
 
+`java.lang.String headlessComponentLink` 
+
+_No Javadoc found_
+
 
 
 
@@ -9506,6 +9533,10 @@ _No Javadoc found_
 
 _No Javadoc found_
 
+`java.lang.String headlessComponentLink` 
+
+_No Javadoc found_
+
 
 
 

_versions/main/guides/dev-ui.adoc

@@ -1295,6 +1295,68 @@ There might be cases where you develop an extension outside of Quarkus core (lik
 
 image::dev-ui-jsonrpc-log-v2.png[alt=Dev UI Json RPC Log,role="center"]
 
+=== Advanced: Headless Components
+
+In rare cases, an extension might need to execute logic *even when its main component is not added to the DOM*. This is typically useful for setting global state or triggering background tasks without displaying any UI.
+
+To support this, extensions can declare a *headless component* — a web component with no visual representation that runs automatically on page load.
+
+Declare the headless component in your extension:
+
+[source,java]
+----
+CardPageBuildItem cardPageBuildItem = new CardPageBuildItem();
+cardPageBuildItem.setHeadlessComponentLink("qwc-chappie-init.js"); // <1>
+----
+<1> Set the path to the headless component JavaScript file (relative to the extension resources).
+
+Then create the component alongside your other Dev UI pages:
+
+[source,javascript]
+----
+import { LitElement } from 'lit';
+import { JsonRpc } from 'jsonrpc';
+import { assistantState } from 'assistant-state';
+
+/**
+ * This load on browser load (headless components) to set the initial assistant state
+ */
+class QwcChappieInit extends LitElement {
+
+    static properties = {
+        namespace: {attribute: true}, // <1>
+    }
+
+    connectedCallback() {
+        super.connectedCallback();
+        this._init().then(() => this.remove()); // <2>
+    }
+
+    async _init() {
+        const jsonRpc = new JsonRpc(this.namespace); // <3>
+
+        jsonRpc.loadConfiguration().then(jsonRpcResponse => { 
+            if(jsonRpcResponse.result && jsonRpcResponse.result.name){
+                assistantState.ready();
+            }else{
+                assistantState.available();
+            }
+        });
+    }
+
+    // prevent rendering anything
+    createRenderRoot() { // <3>
+        return this;
+    }
+}
+customElements.define('qwc-chappie-init', QwcChappieInit); // <4>
+----
+<1> The `namespace` attribute will always be provided automatically by Dev UI.
+<2> Perform your logic in `connectedCallback`, then remove the element if no longer needed.
+<3> When using JsonRPC, pass in the provided namespace (instead of `this`, as in normal components).
+<4> Your tag definition have to be the filename without the `.js`
+
+
 === Testing
 
 You can add tests to your extension that test: