THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Sending POJOs to the JPA endpoint inserts entities into the database. The body of the message is assumed to be an entity bean (i.e. a POJO with an @Entity annotation on it).
If the body does not contain an entity bean then use a Message Translator in front of the endpoint to perform the necessary conversion first.
...
Consuming messages removes (or updates) entities in the database. This allows you to use a database table as a logical queue, consumerse consumers take messages from the queue and then delete/update them to logically remove them from the queue.
If you do not wish to delete the entity when it has been processed you can specify ?consumeDelete=false on the URI. This will result in the entity being processed each poll.
...
For sending to the endpoint, the entityClassName is optional. If specified it is used to help use the Type Conversion to ensure the body is of the correct type.
For consuming the entityClassName is mandatory.
Options
Name | Default Value | Description |
|---|---|---|
entityType | entityClassName | Is the provided entityClassName from the URI |
persistenceUnit | camel | the JPA persistence unit used by default |
consumeDelete | true | Option for JpaConsumer only. Enables / disables whether or not the entity is deleted after it is consumed. |
consumeLockEntity | true | Option for JpaConsumer only. Enables / disables whether or not to use exclusive locking of each entity while processing the results from the pooling. |
flushOnSend | true | Option for JpaProducer only. Flushes the EntityManager after the entity beans has been persisted. |
maximumResults | -1 | Option for JpaConsumer only. Set the maximum number of results to retrieve on the Query. |
| Include Page | ||||
|---|---|---|---|---|
|