...
Name | Default Value | Description |
---|---|---|
| entityClassName | Overrides the entityClassName from the URI. |
|
| The JPA persistence unit used by default. |
|
| JPA consumer only: If |
|
| JPA consumer only: Specifies whether or not to set an exclusive lock on each entity bean while processing the results from polling. |
|
| JPA producer only: Flushes the EntityManager after the entity bean has been persisted. |
|
| JPA consumer only: Set the maximum number of results to retrieve on the Query. |
|
| This option is Registry based which requires the |
|
| JPA consumer only: Delay in milliseconds between each poll. |
|
| JPA consumer only: Milliseconds before polling starts. |
|
| JPA consumer only: Set to |
|
| JPA consumer only: An integer value to define the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to avoid polling many thousands of messages when starting up the server. Set a value of 0 or negative to disable. |
|
| JPA consumer only: To use a custom query when consuming data. |
|
| JPA consumer only: To use a named query when consuming data. |
|
| JPA consumer only: To use a custom native query when consuming data. You may want to use the option |
|
| Camel 2.12: JPA consumer only: This option is Registry based which requires the |
|
| Camel 2.7: JPA consumer only: Defines the type of the returned payload (we will call |
|
| Camel 2.7.5/2.8.3/2.9: JPA consumer only: Whether to run the consumer in transacted mode, by which all messages will either commit or rollback, when the entire batch has been processed. The default behavior (false) is to commit all the previously successfully processed messages, and only rollback the last failed message. |
|
| Camel 2.11.2/2.12: To configure the lock mode on the consumer. The possible values is defined in the enum |
|
| Camel 2.13: To configure whether to use NOWAIT on lock and silently skip the entity. |
|
| Camel 2.5: JPA producer only: Indicates to use |
|
| Camel 2.12.3: camel-jpa will join transaction by default from Camel 2.12 onwards. 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 |
usePassedInEntityManager | false | Camel 2.12.4/2.13.1 JPA producer only: If set to true, then Camel will use the EntityManager from the header JpaConstants.ENTITYMANAGER instead of the configured entity manager on the component/endpoint. This allows end users to control which entity manager will be in use. |
Message Headers
Camel adds the following message headers to the exchange:
...