Repository: camel Updated Branches: refs/heads/master 1fd504a12 -> a39f31336
http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc b/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc index 64405af..b38b2e0 100644 --- a/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc +++ b/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc @@ -48,10 +48,10 @@ The Atmosphere Websocket component supports 7 options which are listed below. | Name | Group | Default | Java Type | Description | servletName | | | String | Default name of servlet to use. The default name is CamelServlet. | httpRegistry | | | HttpRegistry | To use a custom org.apache.camel.component.servlet.HttpRegistry. -| attachmentMultipartBinding | | | boolean | Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's. +| attachmentMultipartBinding | | false | boolean | Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's. | httpBinding | | | HttpBinding | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | httpConfiguration | | | HttpConfiguration | To use the shared HttpConfiguration as base configuration. -| allowJavaSerializedObject | | | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. +| allowJavaSerializedObject | | false | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | headerFilterStrategy | | | HeaderFilterStrategy | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. |======================================================================= {% endraw %} http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-disruptor/src/main/docs/disruptor-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc b/components/camel-disruptor/src/main/docs/disruptor-component.adoc index 99a59e6..8ac5679 100644 --- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc +++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc @@ -109,7 +109,7 @@ The Disruptor component supports 7 options which are listed below. |======================================================================= | Name | Group | Default | Java Type | Description | defaultConcurrentConsumers | | 1 | int | To configure the default number of concurrent consumers -| defaultMultipleConsumers | | | boolean | To configure the default value for multiple consumers +| defaultMultipleConsumers | | false | boolean | To configure the default value for multiple consumers | defaultProducerType | | Multi | DisruptorProducerType | To configure the default value for DisruptorProducerType The default value is Multi. | defaultWaitStrategy | | Blocking | DisruptorWaitStrategy | To configure the default value for DisruptorWaitStrategy The default value is Blocking. | defaultBlockWhenFull | | true | boolean | To configure the default value for block when full The default value is true. http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-http/src/main/docs/http-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-http/src/main/docs/http-component.adoc b/components/camel-http/src/main/docs/http-component.adoc index 7aebd67..a306738 100644 --- a/components/camel-http/src/main/docs/http-component.adoc +++ b/components/camel-http/src/main/docs/http-component.adoc @@ -132,7 +132,7 @@ The HTTP component supports 6 options which are listed below. | httpConnectionManager | | | HttpConnectionManager | To use a custom HttpConnectionManager to manage connections | httpBinding | | | HttpBinding | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | httpConfiguration | | | HttpConfiguration | To use the shared HttpConfiguration as base configuration. -| allowJavaSerializedObject | | | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. +| allowJavaSerializedObject | | false | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | headerFilterStrategy | | | HeaderFilterStrategy | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. |======================================================================= {% endraw %} http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-http4/src/main/docs/http4-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-http4/src/main/docs/http4-component.adoc b/components/camel-http4/src/main/docs/http4-component.adoc index 8a5a06f..c71390d 100644 --- a/components/camel-http4/src/main/docs/http4-component.adoc +++ b/components/camel-http4/src/main/docs/http4-component.adoc @@ -69,7 +69,7 @@ The HTTP4 component supports 13 options which are listed below. | clientConnectionManager | | | HttpClientConnectionManager | To use a custom HttpClientConnectionManager to manage connections | httpBinding | | | HttpBinding | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | httpConfiguration | | | HttpConfiguration | To use the shared HttpConfiguration as base configuration. -| allowJavaSerializedObject | | | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. +| allowJavaSerializedObject | | false | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | httpContext | | | HttpContext | To use a custom org.apache.http.protocol.HttpContext when executing requests. | sslContextParameters | | | SSLContextParameters | To configure security using SSLContextParameters. Important: Only one instance of org.apache.camel.util.jsse.SSLContextParameters is supported per HttpComponent. If you need to use 2 or more different instances you need to define a new HttpComponent per instance you need. | x509HostnameVerifier | | | X509HostnameVerifier | To use a custom X509HostnameVerifier such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier. http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-jetty9/src/main/docs/jetty-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-jetty9/src/main/docs/jetty-component.adoc b/components/camel-jetty9/src/main/docs/jetty-component.adoc index 120be69..d24b789 100644 --- a/components/camel-jetty9/src/main/docs/jetty-component.adoc +++ b/components/camel-jetty9/src/main/docs/jetty-component.adoc @@ -73,7 +73,7 @@ The Jetty 9 component supports 31 options which are listed below. | minThreads | | | Integer | To set a value for minimum number of threads in server thread pool. Notice that both a min and max size must be configured. | maxThreads | | | Integer | To set a value for maximum number of threads in server thread pool. Notice that both a min and max size must be configured. | threadPool | | | ThreadPool | To use a custom thread pool for the server. This option should only be used in special circumstances. -| enableJmx | | | boolean | If this option is true Jetty JMX support will be enabled for this endpoint. +| enableJmx | | false | boolean | If this option is true Jetty JMX support will be enabled for this endpoint. | jettyHttpBinding | | | JettyHttpBinding | To use a custom org.apache.camel.component.jetty.JettyHttpBinding which are used to customize how a response should be written for the producer. | httpBinding | | | HttpBinding | Not to be used - use JettyHttpBinding instead. | httpConfiguration | | | HttpConfiguration | Jetty component does not use HttpConfiguration. @@ -89,9 +89,9 @@ The Jetty 9 component supports 31 options which are listed below. | responseHeaderSize | | | Integer | Allows to configure a custom value of the response header size on the Jetty connectors. | proxyHost | | | String | To use a http proxy to configure the hostname. | proxyPort | | | Integer | To use a http proxy to configure the port number. -| useXForwardedForHeader | | | boolean | To use the X-Forwarded-For header in HttpServletRequest.getRemoteAddr. +| useXForwardedForHeader | | false | boolean | To use the X-Forwarded-For header in HttpServletRequest.getRemoteAddr. | sendServerVersion | | true | boolean | If the option is true jetty server will send the date header to the client which sends the request. NOTE please make sure there is no any other camel-jetty endpoint is share the same port otherwise this option may not work as expected. -| allowJavaSerializedObject | | | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. +| allowJavaSerializedObject | | false | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | headerFilterStrategy | | | HeaderFilterStrategy | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. |======================================================================= {% endraw %} http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-jgroups/src/main/docs/jgroups-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-jgroups/src/main/docs/jgroups-component.adoc b/components/camel-jgroups/src/main/docs/jgroups-component.adoc index 01e4832..15a6ca3 100644 --- a/components/camel-jgroups/src/main/docs/jgroups-component.adoc +++ b/components/camel-jgroups/src/main/docs/jgroups-component.adoc @@ -65,7 +65,7 @@ The JGroups component supports 3 options which are listed below. | Name | Group | Default | Java Type | Description | channel | | | Channel | Channel to use | channelProperties | | | String | Specifies configuration properties of the JChannel used by the endpoint. -| enableViewMessages | | | boolean | If set to true the consumer endpoint will receive org.jgroups.View messages as well (not only org.jgroups.Message instances). By default only regular messages are consumed by the endpoint. +| enableViewMessages | | false | boolean | If set to true the consumer endpoint will receive org.jgroups.View messages as well (not only org.jgroups.Message instances). By default only regular messages are consumed by the endpoint. |======================================================================= {% endraw %} // component options: END http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-jms/src/main/docs/jms-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-jms/src/main/docs/jms-component.adoc b/components/camel-jms/src/main/docs/jms-component.adoc index 07fdaa8..969b86a 100644 --- a/components/camel-jms/src/main/docs/jms-component.adoc +++ b/components/camel-jms/src/main/docs/jms-component.adoc @@ -223,10 +223,10 @@ The JMS component supports 74 options which are listed below. |======================================================================= | Name | Group | Default | Java Type | Description | configuration | | | JmsConfiguration | To use a shared JMS configuration -| acceptMessagesWhileStopping | | | boolean | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option if you start and stop JMS routes at runtime while there are still messages enqueued on the queue. If this option is false and you stop the JMS route then messages may be rejected and the JMS broker would have to attempt redeliveries which yet again may be rejected and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option. -| allowReplyManagerQuickStop | | | boolean | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfigurationisAcceptMessagesWhileStopping is enabled and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag. +| acceptMessagesWhileStopping | | false | boolean | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option if you start and stop JMS routes at runtime while there are still messages enqueued on the queue. If this option is false and you stop the JMS route then messages may be rejected and the JMS broker would have to attempt redeliveries which yet again may be rejected and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option. +| allowReplyManagerQuickStop | | false | boolean | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfigurationisAcceptMessagesWhileStopping is enabled and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag. | acknowledgementMode | | | int | The JMS acknowledgement mode defined as an Integer. Allows you to set vendor-specific extensions to the acknowledgment mode. For the regular modes it is preferable to use the acknowledgementModeName instead. -| eagerLoadingOfProperties | | | boolean | Enables eager loading of JMS properties as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties +| eagerLoadingOfProperties | | false | boolean | Enables eager loading of JMS properties as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties | acknowledgementModeName | | AUTO_ACKNOWLEDGE | String | The JMS acknowledgement name which is one of: SESSION_TRANSACTED CLIENT_ACKNOWLEDGE AUTO_ACKNOWLEDGE DUPS_OK_ACKNOWLEDGE | autoStartup | | true | boolean | Specifies whether the consumer container should auto-startup. | cacheLevel | | | int | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. @@ -246,7 +246,7 @@ The JMS component supports 74 options which are listed below. | errorHandlerLoggingLevel | | WARN | LoggingLevel | Allows to configure the default errorHandler logging level for logging uncaught exceptions. | errorHandlerLogStackTrace | | true | boolean | Allows to control whether stacktraces should be logged or not by the default errorHandler. | explicitQosEnabled | | false | boolean | Set if the deliveryMode priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option which operates at message granularity reading QoS properties exclusively from the Camel In message headers. -| exposeListenerSession | | | boolean | Specifies whether the listener session should be exposed when consuming messages. +| exposeListenerSession | | false | boolean | Specifies whether the listener session should be exposed when consuming messages. | idleTaskExecutionLimit | | 1 | int | Specifies the limit for idle executions of a receive task not having received any message within its execution. If this limit is reached the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | idleConsumerLimit | | 1 | int | Specify the limit for the number of consumers that are allowed to be idle at any given time. | maxConcurrentConsumers | | | int | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. @@ -257,37 +257,37 @@ The JMS component supports 74 options which are listed below. | mapJmsMessage | | true | boolean | Specifies whether Camel should auto map the received JMS message to a suited payload type such as javax.jms.TextMessage to a String etc. See section about how mapping works below for more details. | messageIdEnabled | | true | boolean | When sending specifies whether message IDs should be added. This is just an hint to the JMS Broker. If the JMS provider accepts this hint these messages must have the message ID set to null; if the provider ignores the hint the message ID must be set to its normal unique value | messageTimestampEnabled | | true | boolean | Specifies whether timestamps should be enabled by default on sending messages. -| alwaysCopyMessage | | | boolean | If true Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations such as when a replyToDestinationSelectorName is set (incidentally Camel will set the alwaysCopyMessage option to true if a replyToDestinationSelectorName is set) -| useMessageIDAsCorrelationID | | | boolean | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. +| alwaysCopyMessage | | false | boolean | If true Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations such as when a replyToDestinationSelectorName is set (incidentally Camel will set the alwaysCopyMessage option to true if a replyToDestinationSelectorName is set) +| useMessageIDAsCorrelationID | | false | boolean | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | priority | | 4 | int | 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. -| pubSubNoLocal | | | boolean | Specifies whether to inhibit the delivery of messages published by its own connection. +| pubSubNoLocal | | false | boolean | Specifies whether to inhibit the delivery of messages published by its own connection. | receiveTimeout | | 1000 | long | The timeout for receiving messages (in milliseconds). | recoveryInterval | | 5000 | long | Specifies the interval between recovery attempts i.e. when a connection is being refreshed in milliseconds. The default is 5000 ms that is 5 seconds. -| subscriptionDurable | | | boolean | Deprecated: Enabled by default if you specify a durableSubscriptionName and a clientId. +| subscriptionDurable | | false | boolean | Deprecated: Enabled by default if you specify a durableSubscriptionName and a clientId. | taskExecutor | | | TaskExecutor | Allows you to specify a custom task executor for consuming messages. | timeToLive | | -1 | long | When sending messages specifies the time-to-live of the message (in milliseconds). -| transacted | | | boolean | Specifies whether to use transacted mode +| transacted | | false | boolean | Specifies whether to use transacted mode | lazyCreateTransactionManager | | true | boolean | If true Camel will create a JmsTransactionManager if there is no transactionManager injected when option transacted=true. | transactionManager | | | PlatformTransactionManager | The Spring transaction manager to use. | transactionName | | | String | The name of the transaction to use. | transactionTimeout | | -1 | int | The timeout value of the transaction (in seconds) if using transacted mode. -| testConnectionOnStartup | | | boolean | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. -| asyncStartListener | | | boolean | Whether to startup the JmsConsumer message listener asynchronously when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true you will let routes startup while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used then beware that if the connection could not be established then an exception is logged at WARN level and the consumer will not be able to receive messages; You can then restart the route to retry. -| asyncStopListener | | | boolean | Whether to stop the JmsConsumer message listener asynchronously when stopping a route. -| forceSendOriginalMessage | | | boolean | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. +| testConnectionOnStartup | | false | boolean | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. +| asyncStartListener | | false | boolean | Whether to startup the JmsConsumer message listener asynchronously when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true you will let routes startup while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used then beware that if the connection could not be established then an exception is logged at WARN level and the consumer will not be able to receive messages; You can then restart the route to retry. +| asyncStopListener | | false | boolean | Whether to stop the JmsConsumer message listener asynchronously when stopping a route. +| forceSendOriginalMessage | | false | boolean | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. | requestTimeout | | 20000 | long | The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. | requestTimeoutCheckerInterval | | 1000 | long | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs then you can lower this interval to check more frequently. The timeout is determined by the option requestTimeout. -| transferExchange | | | boolean | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body Out body Fault body In headers Out headers Fault headers exchange properties exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side so Camel knows the payloads is an Exchange and not a regular payload. -| transferException | | | boolean | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. -| transferFault | | | boolean | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed with a SOAP fault (not exception) on the consumer side then the fault flag on link org.apache.camel.MessageisFault() will be send back in the response as a JMS header with the key link JmsConstantsJMS_TRANSFER_FAULT. If the client is Camel the returned fault flag will be set on the link org.apache.camel.MessagesetFault(boolean). You may want to enable this when using Camel components that support faults such as SOAP based such as cxf or spring-ws. +| transferExchange | | false | boolean | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body Out body Fault body In headers Out headers Fault headers exchange properties exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side so Camel knows the payloads is an Exchange and not a regular payload. +| transferException | | false | boolean | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. +| transferFault | | false | boolean | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed with a SOAP fault (not exception) on the consumer side then the fault flag on link org.apache.camel.MessageisFault() will be send back in the response as a JMS header with the key link JmsConstantsJMS_TRANSFER_FAULT. If the client is Camel the returned fault flag will be set on the link org.apache.camel.MessagesetFault(boolean). You may want to enable this when using Camel components that support faults such as SOAP based such as cxf or spring-ws. | jmsOperations | | | JmsOperations | Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose but not used much as stated in the spring API docs. | destinationResolver | | | DestinationResolver | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example to lookup the real destination in a JNDI registry). | replyToType | | | ReplyToType | 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. -| preserveMessageQos | | | boolean | Set to true if you want to send message using the QoS settings specified on the message instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority JMSDeliveryMode and JMSExpiration. You can provide all or only some of them. If not provided Camel will fall back to use the values from the endpoint instead. So when using this option the headers override the values from the endpoint. The explicitQosEnabled option by contrast will only use options set on the endpoint and not values from the message header. -| asyncConsumer | | | boolean | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100 strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled then asyncConsumer=true does not run asynchronously as transaction must be executed synchronously (Camel 3.0 may support async transactions). +| preserveMessageQos | | false | boolean | Set to true if you want to send message using the QoS settings specified on the message instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority JMSDeliveryMode and JMSExpiration. You can provide all or only some of them. If not provided Camel will fall back to use the values from the endpoint instead. So when using this option the headers override the values from the endpoint. The explicitQosEnabled option by contrast will only use options set on the endpoint and not values from the message header. +| asyncConsumer | | false | boolean | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100 strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled then asyncConsumer=true does not run asynchronously as transaction must be executed synchronously (Camel 3.0 may support async transactions). | allowNullBody | | true | boolean | Whether to allow sending messages with no body. If this option is false and the message body is null then an JMSException is thrown. -| includeSentJMSMessageID | | | boolean | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. -| includeAllJMSXProperties | | | boolean | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. +| includeSentJMSMessageID | | false | boolean | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. +| includeAllJMSXProperties | | false | boolean | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | defaultTaskExecutorType | | | DefaultTaskExecutorType | Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set it defaults to the previous behaviour which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers. | jmsKeyFormatStrategy | | | JmsKeyFormatStrategy | 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. | applicationContext | | | ApplicationContext | Sets the Spring ApplicationContext to use http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-jpa/src/main/docs/jpa-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-jpa/src/main/docs/jpa-component.adoc b/components/camel-jpa/src/main/docs/jpa-component.adoc index 73f6f5b..f017236 100644 --- a/components/camel-jpa/src/main/docs/jpa-component.adoc +++ b/components/camel-jpa/src/main/docs/jpa-component.adoc @@ -103,7 +103,7 @@ The JPA component supports 4 options which are listed below. | entityManagerFactory | | | EntityManagerFactory | To use the EntityManagerFactory. This is strongly recommended to configure. | transactionManager | | | PlatformTransactionManager | To use the PlatformTransactionManager for managing transactions. | joinTransaction | | true | boolean | The camel-jpa component will join transaction by default. You can use this option to turn this off for example if you use LOCAL_RESOURCE and join transaction doesn't work with your JPA provider. This option can also be set globally on the JpaComponent instead of having to set it on all endpoints. -| sharedEntityManager | | | boolean | Whether to use Spring's SharedEntityManager for the consumer/producer. Note in most cases joinTransaction should be set to false as this is not an EXTENDED EntityManager. +| sharedEntityManager | | false | boolean | Whether to use Spring's SharedEntityManager for the consumer/producer. Note in most cases joinTransaction should be set to false as this is not an EXTENDED EntityManager. |======================================================================= {% endraw %} // component options: END http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-jsch/src/main/docs/scp-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-jsch/src/main/docs/scp-component.adoc b/components/camel-jsch/src/main/docs/scp-component.adoc index d895d43..8de2509 100644 --- a/components/camel-jsch/src/main/docs/scp-component.adoc +++ b/components/camel-jsch/src/main/docs/scp-component.adoc @@ -53,7 +53,7 @@ The SCP component supports 1 options which are listed below. [width="100%",cols="2,1,1m,1m,5",options="header"] |======================================================================= | Name | Group | Default | Java Type | Description -| verboseLogging | | | boolean | JSCH is verbose logging out of the box. Therefore we turn the logging down to DEBUG logging by default. But setting this option to true turns on the verbose logging again. +| verboseLogging | | false | boolean | JSCH is verbose logging out of the box. Therefore we turn the logging down to DEBUG logging by default. But setting this option to true turns on the verbose logging again. |======================================================================= {% endraw %} // component options: END http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-quartz2/src/main/docs/quartz2-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-quartz2/src/main/docs/quartz2-component.adoc b/components/camel-quartz2/src/main/docs/quartz2-component.adoc index 85fd477..8d80737 100644 --- a/components/camel-quartz2/src/main/docs/quartz2-component.adoc +++ b/components/camel-quartz2/src/main/docs/quartz2-component.adoc @@ -63,7 +63,7 @@ The Quartz2 component supports 9 options which are listed below. | Name | Group | Default | Java Type | Description | autoStartScheduler | | true | boolean | Whether or not the scheduler should be auto started. This options is default true | startDelayedSeconds | | | int | Seconds to wait before starting the quartz scheduler. -| prefixJobNameWithEndpointId | | | boolean | Whether to prefix the quartz job with the endpoint id. This option is default false. +| prefixJobNameWithEndpointId | | false | boolean | Whether to prefix the quartz job with the endpoint id. This option is default false. | enableJmx | | true | boolean | Whether to enable Quartz JMX which allows to manage the Quartz scheduler from JMX. This options is default true | properties | | | Properties | Properties to configure the Quartz scheduler. | propertiesFile | | | String | File name of the properties to load from the classpath http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-quickfix/src/main/docs/quickfix-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-quickfix/src/main/docs/quickfix-component.adoc b/components/camel-quickfix/src/main/docs/quickfix-component.adoc index fec1290..e39e750 100644 --- a/components/camel-quickfix/src/main/docs/quickfix-component.adoc +++ b/components/camel-quickfix/src/main/docs/quickfix-component.adoc @@ -103,7 +103,7 @@ The QuickFix component supports 5 options which are listed below. | logFactory | | | LogFactory | To use the given LogFactory | messageStoreFactory | | | MessageStoreFactory | To use the given MessageStoreFactory | configurations | | | Map | To use the given map of pre configured QuickFix configurations mapped to the key -| lazyCreateEngines | | | boolean | If set to true the engines will be created and started when needed (when first message is send) +| lazyCreateEngines | | false | boolean | If set to true the engines will be created and started when needed (when first message is send) |======================================================================= {% endraw %} // component options: END http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-restlet/src/main/docs/restlet-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-restlet/src/main/docs/restlet-component.adoc b/components/camel-restlet/src/main/docs/restlet-component.adoc index 73ed736..9006cfd 100644 --- a/components/camel-restlet/src/main/docs/restlet-component.adoc +++ b/components/camel-restlet/src/main/docs/restlet-component.adoc @@ -89,7 +89,7 @@ The Restlet component supports 20 options which are listed below. | useForwardedForHeader | | | Boolean | Lookup the X-Forwarded-For header supported by popular proxies and caches and uses it to populate the Request.getClientAddresses() method result. This information is only safe for intermediary components within your local network. Other addresses could easily be changed by setting a fake header and should not be trusted for serious security checks. | reuseAddress | | | Boolean | Enable/disable the SO_REUSEADDR socket option. See java.io.ServerSocketreuseAddress property for additional details. | maxQueued | | | Integer | Maximum number of calls that can be queued if there aren't any worker thread available to service them. If the value is '0' then no queue is used and calls are rejected if no worker thread is immediately available. If the value is '-1' then an unbounded queue is used and calls are never rejected. -| disableStreamCache | | | boolean | Determines whether or not the raw input stream from Restlet is cached or not (Camel will read the stream into a in memory/overflow to file Stream caching) cache. By default Camel will cache the Restlet input stream to support reading it multiple times to ensure Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream such as streaming it directly to a file or other persistent store. DefaultRestletBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support reading the stream multiple times. +| disableStreamCache | | false | boolean | Determines whether or not the raw input stream from Restlet is cached or not (Camel will read the stream into a in memory/overflow to file Stream caching) cache. By default Camel will cache the Restlet input stream to support reading it multiple times to ensure Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream such as streaming it directly to a file or other persistent store. DefaultRestletBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support reading the stream multiple times. | port | | | int | To configure the port number for the restlet consumer routes. This allows to configure this once to reuse the same port for these consumers. | synchronous | | | Boolean | Whether to use synchronous Restlet Client for the producer. Setting this option to true can yield faster performance as it seems the Restlet synchronous Client works better. | enabledConverters | | | List | A list of converters to enable as full class name or simple class name. All the converters automatically registered are enabled if empty or null http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc b/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc index 9ca4211..7ab485c 100644 --- a/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc +++ b/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc @@ -470,13 +470,13 @@ The Salesforce component supports 16 options which are listed below. | httpProxyPort | | | Integer | To configure HTTP proxy port | httpProxyUsername | | | String | To configure HTTP proxy username | httpProxyPassword | | | String | To configure HTTP proxy password -| isHttpProxySocks4 | | | boolean | Enable for Socks4 proxy false by default -| isHttpProxySecure | | | boolean | Enable for TLS connections true by default +| isHttpProxySocks4 | | false | boolean | Enable for Socks4 proxy false by default +| isHttpProxySecure | | false | boolean | Enable for TLS connections true by default | httpProxyIncludedAddresses | | | Set | HTTP proxy included addresses | httpProxyExcludedAddresses | | | Set | HTTP proxy excluded addresses | httpProxyAuthUri | | | String | HTTP proxy authentication URI | httpProxyRealm | | | String | HTTP proxy authentication realm -| httpProxyUseDigestAuth | | | boolean | Use HTTP proxy Digest authentication false by default +| httpProxyUseDigestAuth | | false | boolean | Use HTTP proxy Digest authentication false by default | packages | | | String[] | Package names to scan for DTO classes (multiple packages can be separated by comma). |======================================================================= {% endraw %} http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-servlet/src/main/docs/servlet-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-servlet/src/main/docs/servlet-component.adoc b/components/camel-servlet/src/main/docs/servlet-component.adoc index 34ce17b..7fc4561 100644 --- a/components/camel-servlet/src/main/docs/servlet-component.adoc +++ b/components/camel-servlet/src/main/docs/servlet-component.adoc @@ -56,10 +56,10 @@ The Servlet component supports 7 options which are listed below. | Name | Group | Default | Java Type | Description | servletName | | | String | Default name of servlet to use. The default name is CamelServlet. | httpRegistry | | | HttpRegistry | To use a custom org.apache.camel.component.servlet.HttpRegistry. -| attachmentMultipartBinding | | | boolean | Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's. +| attachmentMultipartBinding | | false | boolean | Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's. | httpBinding | | | HttpBinding | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | httpConfiguration | | | HttpConfiguration | To use the shared HttpConfiguration as base configuration. -| allowJavaSerializedObject | | | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. +| allowJavaSerializedObject | | false | boolean | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | headerFilterStrategy | | | HeaderFilterStrategy | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. |======================================================================= {% endraw %} http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/camel-websocket/src/main/docs/websocket-component.adoc ---------------------------------------------------------------------- diff --git a/components/camel-websocket/src/main/docs/websocket-component.adoc b/components/camel-websocket/src/main/docs/websocket-component.adoc index 0618cc8..0a3d2c8 100644 --- a/components/camel-websocket/src/main/docs/websocket-component.adoc +++ b/components/camel-websocket/src/main/docs/websocket-component.adoc @@ -52,7 +52,7 @@ The Jetty Websocket component supports 12 options which are listed below. | sslKeyPassword | | | String | The password for the keystore when using SSL. | sslPassword | | | String | The password when using SSL. | sslKeystore | | | String | The path to the keystore. -| enableJmx | | | boolean | If this option is true Jetty JMX support will be enabled for this endpoint. See Jetty JMX support for more details. +| enableJmx | | false | boolean | If this option is true Jetty JMX support will be enabled for this endpoint. See Jetty JMX support for more details. | minThreads | | | Integer | To set a value for minimum number of threads in server thread pool. MaxThreads/minThreads or threadPool fields are required due to switch to Jetty9. The default values for minThreads is 1. | maxThreads | | | Integer | To set a value for maximum number of threads in server thread pool. MaxThreads/minThreads or threadPool fields are required due to switch to Jetty9. The default values for maxThreads is 1 2 noCores. | threadPool | | | ThreadPool | To use a custom thread pool for the server. MaxThreads/minThreads or threadPool fields are required due to switch to Jetty9. http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/components/readme.adoc ---------------------------------------------------------------------- diff --git a/components/readme.adoc b/components/readme.adoc index 972b0f3..5c86856 100644 --- a/components/readme.adoc +++ b/components/readme.adoc @@ -204,6 +204,9 @@ Components | link:camel-google-mail/src/main/docs/google-mail-component.adoc[Google Mail] (camel-google-mail) + `google-mail:apiName/methodName` | The google-mail component provides access to Google Mail. +| link:camel-google-pubsub/src/main/docs/google-pubsub-component.adoc[Google Pubsub] (camel-google-pubsub) + +`google-pubsub:projectId:destinationName` | Messaging client for Google Cloud Platform PubSub Service: https://cloud.google.com/pubsub/ + | link:camel-gora/src/main/docs/gora-component.adoc[Gora] (camel-gora) + `gora:name` | The gora component allows you to work with NoSQL databases using the Apache Gora framework. @@ -339,6 +342,9 @@ Components | link:camel-mongodb/src/main/docs/mongodb-component.adoc[MongoDB] (camel-mongodb) + `mongodb:connectionBean` | Component for working with documents stored in MongoDB database. +| link:camel-mongodb3/src/main/docs/mongodb3-component.adoc[MongoDB] (camel-mongodb3) + +`mongodb3:connectionBean` | Component for working with documents stored in MongoDB database. + | link:camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc[MongoDBGridFS] (camel-mongodb-gridfs) + `gridfs:connectionBean` | Component for working with MongoDB GridFS. @@ -378,6 +384,24 @@ Components | link:camel-openshift/src/main/docs/openshift-component.adoc[OpenShift] (camel-openshift) + `openshift:clientId` | *deprecated* To manage your Openshift 2.x applications. +| link:camel-openstack/src/main/docs/openstack-cinder-component.adoc[OpenStack Cinder] (camel-openstack) + +`openstack-cinder:host` | The openstack-cinder component allows messages to be sent to an OpenStack block storage services. + +| link:camel-openstack/src/main/docs/openstack-glance-component.adoc[OpenStack Glance] (camel-openstack) + +`openstack-glance:host` | The openstack-glance component allows messages to be sent to an OpenStack image services. + +| link:camel-openstack/src/main/docs/openstack-keystone-component.adoc[OpenStack Keystone] (camel-openstack) + +`openstack-keystone:host` | The openstack-keystone component allows messages to be sent to an OpenStack identity services. + +| link:camel-openstack/src/main/docs/openstack-neutron-component.adoc[OpenStack Neutron] (camel-openstack) + +`openstack-neutron:host` | The openstack-neutron component allows messages to be sent to an OpenStack network services. + +| link:camel-openstack/src/main/docs/openstack-nova-component.adoc[OpenStack Nova] (camel-openstack) + +`openstack-nova:host` | The openstack-nova component allows messages to be sent to an OpenStack compute services. + +| link:camel-openstack/src/main/docs/openstack-swift-component.adoc[OpenStack Swift] (camel-openstack) + +`openstack-swift:host` | The openstack-swift component allows messages to be sent to an OpenStack object storage services. + | link:camel-optaplanner/src/main/docs/optaplanner-component.adoc[OptaPlanner] (camel-optaplanner) + `optaplanner:configFile` | Solves the planning problem contained in a message with OptaPlanner. http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/docs/user-manual/en/SUMMARY.md ---------------------------------------------------------------------- diff --git a/docs/user-manual/en/SUMMARY.md b/docs/user-manual/en/SUMMARY.md index bdcce6d..e6c39fb 100644 --- a/docs/user-manual/en/SUMMARY.md +++ b/docs/user-manual/en/SUMMARY.md @@ -190,6 +190,7 @@ * [Google Calendar](google-calendar-component.adoc) * [Google Drive](google-drive-component.adoc) * [Google Mail](google-mail-component.adoc) + * [Google Pubsub](google-pubsub-component.adoc) * [Gora](gora-component.adoc) * [Grape](grape-component.adoc) * [Guava EventBus](guava-eventbus-component.adoc) @@ -235,6 +236,7 @@ * [Mina2](mina2-component.adoc) * [MLLP](mllp-component.adoc) * [MongoDB](mongodb-component.adoc) + * [MongoDB](mongodb3-component.adoc) * [MongoDBGridFS](gridfs-component.adoc) * [MQTT](mqtt-component.adoc) * [MSV](msv-component.adoc) @@ -248,6 +250,12 @@ * [Netty4](netty4-component.adoc) * [Netty4 HTTP](netty4-http-component.adoc) * [OpenShift](openshift-component.adoc) + * [OpenStack Cinder](openstack-cinder-component.adoc) + * [OpenStack Glance](openstack-glance-component.adoc) + * [OpenStack Keystone](openstack-keystone-component.adoc) + * [OpenStack Neutron](openstack-neutron-component.adoc) + * [OpenStack Nova](openstack-nova-component.adoc) + * [OpenStack Swift](openstack-swift-component.adoc) * [OptaPlanner](optaplanner-component.adoc) * [OSGi EventAdmin](eventadmin-component.adoc) * [OSGi PAX Logging](paxlogging-component.adoc) http://git-wip-us.apache.org/repos/asf/camel/blob/a39f3133/tooling/apt/src/main/java/org/apache/camel/tools/apt/EndpointAnnotationProcessor.java ---------------------------------------------------------------------- diff --git a/tooling/apt/src/main/java/org/apache/camel/tools/apt/EndpointAnnotationProcessor.java b/tooling/apt/src/main/java/org/apache/camel/tools/apt/EndpointAnnotationProcessor.java index 446aa61..c072cc9 100644 --- a/tooling/apt/src/main/java/org/apache/camel/tools/apt/EndpointAnnotationProcessor.java +++ b/tooling/apt/src/main/java/org/apache/camel/tools/apt/EndpointAnnotationProcessor.java @@ -301,7 +301,10 @@ public class EndpointAnnotationProcessor extends AbstractProcessor { doc = sanitizeDescription(doc, false); Boolean required = entry.getRequired() != null ? Boolean.valueOf(entry.getRequired()) : null; String defaultValue = entry.getDefaultValue(); - // component option do not have default value for boolean (as we dont really known if its true or false) + if (Strings.isNullOrEmpty(defaultValue) && "boolean".equals(entry.getType())) { + // fallback as false for boolean types + defaultValue = "false"; + } // component options do not have prefix String optionalPrefix = "";
