Skip to content

Commit

Permalink
Regen catalog
Browse files Browse the repository at this point in the history
  • Loading branch information
@oscerd
oscerd committed Dec 14, 2020
1 parent 163d42d commit e96bf49
Show file tree
Hide file tree
Showing 239 changed files with 6,580 additions and 771 deletions.
108 changes: 95 additions & 13 deletions camel-kafka-connector-catalog/src/generated/resources/connectors/camel-activemq-sink.json
View file
Expand Up @@ -14,7 +14,13 @@
"description": "The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic]",
"defaultValue": "\"queue\"",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"queue",
"topic",
"temp-queue",
"temp-topic"
]
},
"camel.sink.path.destinationName": {
"name": "camel.sink.path.destinationName",
Expand Down Expand Up @@ -51,7 +57,14 @@
"name": "camel.sink.endpoint.jmsMessageType",
"description": "Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. One of: [Bytes] [Map] [Object] [Stream] [Text]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"Bytes",
"Map",
"Object",
"Stream",
"Text"
]
},
"camel.sink.endpoint.replyTo": {
"name": "camel.sink.endpoint.replyTo",
Expand All @@ -77,7 +90,11 @@
"name": "camel.sink.endpoint.deliveryMode",
"description": "Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"1",
"2"
]
},
"camel.sink.endpoint.deliveryPersistent": {
"name": "camel.sink.endpoint.deliveryPersistent",
Expand Down Expand Up @@ -119,7 +136,18 @@
"description": "Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9]",
"defaultValue": "4",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"1",
"2",
"3",
"4",
"5",
"6",
"7",
"8",
"9"
]
},
"camel.sink.endpoint.replyToConcurrentConsumers": {
"name": "camel.sink.endpoint.replyToConcurrentConsumers",
Expand Down Expand Up @@ -151,7 +179,12 @@
"name": "camel.sink.endpoint.replyToType",
"description": "Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request\/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive. One of: [Temporary] [Shared] [Exclusive]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"Temporary",
"Shared",
"Exclusive"
]
},
"camel.sink.endpoint.requestTimeout": {
"name": "camel.sink.endpoint.requestTimeout",
Expand Down Expand Up @@ -218,7 +251,14 @@
"name": "camel.sink.endpoint.replyToCacheLevelName",
"description": "Sets the cache level by name for the reply consumer when doing request\/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w\/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary queues then CACHE_NONE is not allowed, and you must use a higher value such as CACHE_CONSUMER or CACHE_SESSION. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"CACHE_AUTO",
"CACHE_CONNECTION",
"CACHE_CONSUMER",
"CACHE_NONE",
"CACHE_SESSION"
]
},
"camel.sink.endpoint.replyToDestinationSelectorName": {
"name": "camel.sink.endpoint.replyToDestinationSelectorName",
Expand Down Expand Up @@ -310,7 +350,11 @@
"name": "camel.sink.endpoint.jmsKeyFormatStrategy",
"description": "Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation. One of: [default] [passthrough]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"default",
"passthrough"
]
},
"camel.sink.endpoint.mapJmsMessage": {
"name": "camel.sink.endpoint.mapJmsMessage",
Expand Down Expand Up @@ -515,7 +559,14 @@
"name": "camel.component.activemq.jmsMessageType",
"description": "Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. One of: [Bytes] [Map] [Object] [Stream] [Text]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"Bytes",
"Map",
"Object",
"Stream",
"Text"
]
},
"camel.component.activemq.replyTo": {
"name": "camel.component.activemq.replyTo",
Expand Down Expand Up @@ -555,7 +606,11 @@
"name": "camel.component.activemq.deliveryMode",
"description": "Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"1",
"2"
]
},
"camel.component.activemq.deliveryPersistent": {
"name": "camel.component.activemq.deliveryPersistent",
Expand Down Expand Up @@ -597,7 +652,18 @@
"description": "Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9]",
"defaultValue": "4",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"1",
"2",
"3",
"4",
"5",
"6",
"7",
"8",
"9"
]
},
"camel.component.activemq.replyToConcurrentConsumers": {
"name": "camel.component.activemq.replyToConcurrentConsumers",
Expand Down Expand Up @@ -629,7 +695,12 @@
"name": "camel.component.activemq.replyToType",
"description": "Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request\/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive. One of: [Temporary] [Shared] [Exclusive]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"Temporary",
"Shared",
"Exclusive"
]
},
"camel.component.activemq.requestTimeout": {
"name": "camel.component.activemq.requestTimeout",
Expand Down Expand Up @@ -696,7 +767,14 @@
"name": "camel.component.activemq.replyToCacheLevelName",
"description": "Sets the cache level by name for the reply consumer when doing request\/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w\/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary queues then CACHE_NONE is not allowed, and you must use a higher value such as CACHE_CONSUMER or CACHE_SESSION. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"CACHE_AUTO",
"CACHE_CONNECTION",
"CACHE_CONSUMER",
"CACHE_NONE",
"CACHE_SESSION"
]
},
"camel.component.activemq.replyToDestinationSelectorName": {
"name": "camel.component.activemq.replyToDestinationSelectorName",
Expand Down Expand Up @@ -809,7 +887,11 @@
"name": "camel.component.activemq.jmsKeyFormatStrategy",
"description": "Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation. One of: [default] [passthrough]",
"priority": "MEDIUM",
"required": "false"
"required": "false",
"enum": [
"default",
"passthrough"
]
},
"camel.component.activemq.mapJmsMessage": {
"name": "camel.component.activemq.mapJmsMessage",
Expand Down

0 comments on commit e96bf49

Please sign in to comment.