Add AMQ Broker and Keycloak integration example

[JinyuChen97]

This example demonstrates integration of Apache ActiveMQ Artemis (AMQ Broker) with Keycloak authentication in a Camel Quarkus application.

Features:

• REST endpoint for order submission with Keycloak authentication
• SOAP endpoint for inventory management with Keycloak security policy
• JMS integration using AMQ Broker for asynchronous order processing
• Admin endpoint with role-based access control (RBAC)
• Keycloak component for user management

The example supports:

• Development mode with Dev Services (auto-start Keycloak and Artemis)
• JVM mode
• Native mode
• Kubernetes deployment with complete YAML manifests and testing guide

[aldettinger]

The platform version should probably be upgraded after the recent release of the camel-quarkus main branch:

Caused by: org.apache.maven.plugin.MojoFailureException: Found 5 consistency issues:
 - Expected <quarkus.platform.group-id>io.quarkus</quarkus.platform.group-id>, found io.quarkus.platform in ./amq-broker-keycloak/pom.xml
 - Expected <quarkus.platform.version>3.36.0</quarkus.platform.version>, found 3.35.1 in ./amq-broker-keycloak/pom.xml
 - Expected <camel-quarkus.platform.group-id>org.apache.camel.quarkus</camel-quarkus.platform.group-id>, found ${quarkus.platform.group-id} in ./amq-broker-keycloak/pom.xml
 - Expected <camel-quarkus.platform.artifact-id>camel-quarkus-bom</camel-quarkus.platform.artifact-id>, found quarkus-camel-bom in ./amq-broker-keycloak/pom.xml
 - Expected <camel-quarkus.platform.version>3.37.0-SNAPSHOT</camel-quarkus.platform.version>, found ${quarkus.platform.version} in ./amq-broker-keycloak/pom.xml

You may want to run mvn org.l2x6.cq:cq-maven-plugin:2.10.0:examples-set-platform -Dcq.camel-quarkus.version=3.37.0-SNAPSHOT

[aldettinger]

Looks a great start, generally speaking, there is a question whether the example could be less verbose ? Like do we really need equals method ? Do we really need that much properties in domain pojos ?

The ideal situation would be that each new lines introduced serves the demo purpose as much as possible. So that, users learning camel are not lost into details and complexities that could live in their own example documetation...

Does it make sense ? it's open for discussion for sure :)

[JinyuChen97]

Looks a great start, generally speaking, there is a question whether the example could be less verbose ? Like do we really need equals method ? Do we really need that much properties in domain pojos ?

The ideal situation would be that each new lines introduced serves the demo purpose as much as possible. So that, users learning camel are not lost into details and complexities that could live in their own example documetation...

Does it make sense ? it's open for discussion for sure :)

thanks for the advice! I have simplify some domain objects, processor... Currently waiting for the feedback from Ivo or Torsten to see if this REST -> SOAP example is fine.

[jamesnetherton]

Heads up that some versions across all other projects have been updated:

• Quarkus platform - 3.36.1
• Quarkus artemis - 3.14.3
• Surefire / Failsafe - 3.5.6

Please ensure this project is updated to be in sync.

[JinyuChen97]

After discussed with Torsten, the example is changed to REST endpoint calls SOAP service synchronously and returns response to client. The order events are asynchronously sent to JMS topic that listen by multiple consumer process events: audit logging, email notification, cache.

[aldettinger]

Ok, a last thing following the route design. Would the name amq-broker-keycloak be what users expect ?
Maybe we could name by keywords ala rest-keycloak-soap-jms ? What do you think ?

[jamesnetherton]

Sorry @JinyuChen97, another request. I just merged #518. Please rebase and add this new project to the list of modules in the root project pom.xml.