Fix #2828: Consolidate JMS AMQP 10 SSL variants into single kamelets (#2831)

Remove separate jms-amqp-10-ssl-source and jms-amqp-10-ssl-sink kamelets
and consolidate SSL/TLS support into the existing jms-amqp-10-source and
jms-amqp-10-sink kamelets. SSL is handled by the Qpid JMS client via the
amqps:// URI scheme, so separate kamelets are unnecessary.

Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: oscerd

docs/modules/ROOT/nav.adoc

@@ -130,8 +130,6 @@
 * xref:jira-update-issue-sink.adoc[]
 * xref:jms-amqp-10-sink.adoc[]
 * xref:jms-amqp-10-source.adoc[]
-* xref:jms-amqp-10-ssl-sink.adoc[]
-* xref:jms-amqp-10-ssl-source.adoc[]
 * xref:jms-apache-artemis-sink.adoc[]
 * xref:jms-apache-artemis-source.adoc[]
 * xref:jms-ibm-mq-sink.adoc[]

docs/modules/ROOT/partials/jms-amqp-10-ssl-sink-description.adoc

@@ -31,7 +31,7 @@ metadata:
 spec:
   definition:
     title: "JMS - AMQP 1.0 Sink"
-    description: "Send data to any AMQP 1.0 compliant message broker by using the Apache Qpid JMS client."
+    description: "Send data to any AMQP 1.0 compliant message broker by using the Apache Qpid JMS client. For SSL/TLS connections, use the amqps:// scheme in the remoteURI and configure SSL transport options as query parameters (e.g. transport.trustStoreLocation, transport.trustStorePassword, transport.keyStoreLocation, transport.keyStorePassword, transport.verifyHost, transport.trustAll)."
     required:
       - destinationName
       - remoteURI
@@ -48,7 +48,7 @@ spec:
         type: string
       remoteURI:
         title: "Broker URL"
-        description: "The JMS URL."
+        description: "The JMS URL. Use the amqps:// scheme for SSL/TLS connections."
         type: string
         example: "amqp://my-host:31616"
   dependencies:

docs/modules/ROOT/partials/jms-amqp-10-ssl-source-description.adoc

@@ -31,7 +31,7 @@ metadata:
 spec:
   definition:
     title: "JMS - AMQP 1.0 Source"
-    description: "Consume data from any AMQP 1.0 compliant message broker by using the Apache Qpid JMS client."
+    description: "Consume data from any AMQP 1.0 compliant message broker by using the Apache Qpid JMS client. For SSL/TLS connections, use the amqps:// scheme in the remoteURI and configure SSL transport options as query parameters (e.g. transport.trustStoreLocation, transport.trustStorePassword, transport.keyStoreLocation, transport.keyStorePassword, transport.verifyHost, transport.trustAll)."
     required:
       - destinationName
       - remoteURI
@@ -48,7 +48,7 @@ spec:
         type: string
       remoteURI:
         title: "Broker URL"
-        description: "The JMS URL."
+        description: "The JMS URL. Use the amqps:// scheme for SSL/TLS connections."
         type: string
         example: "amqp://my-host:31616"
   dependencies:

kamelets/jms-amqp-10-sink.kamelet.yaml

@@ -78,7 +78,6 @@ public enum KameletPrefixSchemeEnum {
     jira_transition_issue("jira-transition-issue", "jira"),
     jira_update_issue("jira-update-issue", "jira"),
     jms_amqp_10("jms-amqp-10", "jms"),
-    jms_amqp_10_ssl("jms-amqp-10-ssl", "jms"),
     jms_apache_artemis("jms-apache-artemis", "jms"),
     jms_ibm_mq("jms-ibm-mq", "jms"),
     kafka("kafka", "kafka"),

kamelets/jms-amqp-10-source.kamelet.yaml

@@ -209,8 +209,6 @@ void testSupportedHeaders() throws Exception {
         verifyHeaders("jira-oauth-source", 3);
         verifyHeaders("jms-amqp-10-source", 15);
         verifyHeaders("jms-amqp-10-sink", 18);
-        verifyHeaders("jms-amqp-10-ssl-source", 15);
-        verifyHeaders("jms-amqp-10-ssl-sink", 18);
         verifyHeaders("jms-apache-artemis-source", 15);
         verifyHeaders("jms-apache-artemis-sink", 18);
         verifyHeaders("jms-ibm-mq-source", 15);

kamelets/jms-amqp-10-ssl-sink.kamelet.yaml

@@ -31,7 +31,7 @@ metadata:
 spec:
   definition:
     title: "JMS - AMQP 1.0 Sink"
-    description: "Send data to any AMQP 1.0 compliant message broker by using the Apache Qpid JMS client."
+    description: "Send data to any AMQP 1.0 compliant message broker by using the Apache Qpid JMS client. For SSL/TLS connections, use the amqps:// scheme in the remoteURI and configure SSL transport options as query parameters (e.g. transport.trustStoreLocation, transport.trustStorePassword, transport.keyStoreLocation, transport.keyStorePassword, transport.verifyHost, transport.trustAll)."
     required:
       - destinationName
       - remoteURI
@@ -48,7 +48,7 @@ spec:
         type: string
       remoteURI:
         title: "Broker URL"
-        description: "The JMS URL."
+        description: "The JMS URL. Use the amqps:// scheme for SSL/TLS connections."
         type: string
         example: "amqp://my-host:31616"
   dependencies: