| // Do not edit directly! |
| // This file was generated by camel-quarkus-maven-plugin:update-extension-doc-page |
| [id="extensions-disruptor"] |
| = Disruptor |
| :linkattrs: |
| :cq-artifact-id: camel-quarkus-disruptor |
| :cq-native-supported: true |
| :cq-status: Stable |
| :cq-status-deprecation: Stable |
| :cq-description: Provides asynchronous SEDA behavior using LMAX Disruptor. |
| :cq-deprecated: false |
| :cq-jvm-since: 1.1.0 |
| :cq-native-since: 1.2.0 |
| |
| ifeval::[{doc-show-badges} == true] |
| [.badges] |
| [.badge-key]##JVM since##[.badge-supported]##1.1.0## [.badge-key]##Native since##[.badge-supported]##1.2.0## |
| endif::[] |
| |
| Provides asynchronous SEDA behavior using LMAX Disruptor. |
| |
| [id="extensions-disruptor-whats-inside"] |
| == What's inside |
| |
| * xref:{cq-camel-components}::disruptor-component.adoc[Disruptor component], URI syntax: `disruptor:name` |
| * xref:{cq-camel-components}::disruptor-component.adoc[Disruptor VM component], URI syntax: `disruptor-vm:name` |
| |
| Please refer to the above links for usage and configuration details. |
| |
| [id="extensions-disruptor-maven-coordinates"] |
| == Maven coordinates |
| |
| https://{link-quarkus-code-generator}/?extension-search=camel-quarkus-disruptor[Create a new project with this extension on {link-quarkus-code-generator}, window="_blank"] |
| |
| Or add the coordinates to your existing project: |
| |
| [source,xml] |
| ---- |
| <dependency> |
| <groupId>org.apache.camel.quarkus</groupId> |
| <artifactId>camel-quarkus-disruptor</artifactId> |
| </dependency> |
| ---- |
| ifeval::[{doc-show-user-guide-link} == true] |
| Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications. |
| endif::[] |
| |
| [id="extensions-disruptor-camel-quarkus-limitations"] |
| == Camel Quarkus limitations |
| |
| The `disruptor-vm` component is not available on Camel Quarkus. This is because it is supposed to provide support for communication across multiple CamelContext instances within a single JVM, but by design, there is always just a single `CamelContext` on Camel Quarkus. Therefore `disruptor-vm` would make no sense. |
| |