...
Sending POJOs to the hibernate endpoint inserts entities into the database. The body of the message is assumed to be an entity bean that you have mapped to a relational table using the hibernate .hbm.xml
files.
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, ; 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.
...
Code Block |
---|
hibernate:[entityClassName][?options]
|
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.
You can append query options to the URI in the following format, ?option=value&option=value&...
Options
Name | Default Value | Description |
---|---|---|
| entityClassName | Is the provided entityClassName from the URI. |
| | Option for HibernateConsumer only. Enables / disables Specifies whether or not the entity is deleted after it is consumed. |
| | Option for HibernateConsumer only. Enables / disables Specifies whether or not to use exclusive locking of each entity while processing the results from the pooling. |
| | Option for HibernateProducer only. Flushes the EntityManager after the entity beans bean has been persisted. |
| | Option for HibernateConsumer only. Set the maximum number of results to retrieve on the Query. |
| | Option for HibernateConsumer only. Delay in millis between each poll. |
| | Option for HibernateConsumer only. Millis before polling starts. |
| | Option for HibernateConsumer only. Set to |
...