| // Do not edit directly! |
| // This file was generated by camel-quarkus-maven-plugin:update-extension-doc-page |
| [id="extensions-grpc"] |
| = gRPC |
| :page-aliases: extensions/grpc.adoc |
| :linkattrs: |
| :cq-artifact-id: camel-quarkus-grpc |
| :cq-native-supported: true |
| :cq-status: Stable |
| :cq-status-deprecation: Stable |
| :cq-description: Expose gRPC endpoints and access external gRPC endpoints. |
| :cq-deprecated: false |
| :cq-jvm-since: 1.0.0 |
| :cq-native-since: 1.0.0 |
| |
| ifeval::[{doc-show-badges} == true] |
| [.badges] |
| [.badge-key]##JVM since##[.badge-supported]##1.0.0## [.badge-key]##Native since##[.badge-supported]##1.0.0## |
| endif::[] |
| |
| Expose gRPC endpoints and access external gRPC endpoints. |
| |
| [id="extensions-grpc-whats-inside"] |
| == What's inside |
| |
| * xref:{cq-camel-components}::grpc-component.adoc[gRPC component], URI syntax: `grpc:host:port/service` |
| |
| Please refer to the above link for usage and configuration details. |
| |
| [id="extensions-grpc-maven-coordinates"] |
| == Maven coordinates |
| |
| https://{link-quarkus-code-generator}/?extension-search=camel-quarkus-grpc[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-grpc</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-grpc-camel-quarkus-limitations"] |
| == Camel Quarkus limitations |
| |
| [id="extensions-grpc-limitations-integration-with-quarkus-grpc-is-not-supported"] |
| === Integration with Quarkus gRPC is not supported |
| |
| At present there is no support for integrating Camel Quarkus gRPC with Quarkus gRPC. If you have both the `camel-quarkus-grpc` and `quarkus-grpc` extension dependency on the classpath, you are likely to encounter problems at build time when compiling your application. |
| |
| [id="extensions-grpc-limitations-protobuf-generated-code"] |
| === Protobuf generated code |
| |
| You can https://github.com/grpc/grpc-java#generated-code[generate] gRPC service stubs with protobuf. A limitation of this is that generated code is annotated with the non Jakarta EE 10 friendly `@javax.annotation.Generated`. |
| |
| To avoid compilation issues, the `grpc-java` project recommendation is to add a `provided` scoped dependency like this: |
| |
| [source,xml] |
| ---- |
| <dependency> |
| <groupId>org.apache.tomcat</groupId> |
| <artifactId>annotations-api</artifactId> |
| <version>6.0.53</version> |
| <scope>provided</scope> |
| </dependency> |
| ---- |
| |
| Alternatively, you can use Maven or Gradle plugins to iterate over the generated code (found at `target/generated-sources` for Maven) and replace all instances of `@javax.annotation.Generated` with `@jakarta.annotation.Generated`. |
| |