Please tell of how to use @Consumed annotation when consuming from JPA??

[rajk1000]

Hi All,

I'm sure this is a common question, and I know this as I have just done a google search on it, and find many people asking this question, but no one really responds with an actual (short, ie 4 lines or so) example, of how to do it. Even Camel In Action has no examples or discussion of how to do this.

When Consuming from a JPA endpoint, the default behaviour is that the row will be deleted from the DB after it is consumed. You can set (consumeDelete=false) to leave the row there even after it has been consumed.

However, this means that the continuous polling of the JPA endpoint will eventually (depending on the polling delay), bring these same rows back again for processing again. This is not what I want.

I want the rows to remain there, but also, to be marked with one column (call it 'processed') set to Y, from N previously etc etc. I understand that this can be done using the @Consumed annotation. However, there are absolutely no examples of this code anywhere.

Can some one please just provide some? Apologies, I am new to Camel, and have not read Camel In Action from cover to cover yet, although it seems a great book.

Also, another question I have are:

- We are planning on using Camel. We will mainly consume from JPA endpoints and produce to JMS endpoints. In terms of JPA, are there any suggestions on which is better , Hibernate or OpenJPA? Any input is appreciated? (Or should we totally forget JPA altogether and just use JDBC. Has Camel been coded to work better with JDBC endpoints rather than JPA?)

Many Thanks for any help offered.

[davsclaus]

Check the unit tests of camel-jpa source code for examples.

[davsclaus]

In here

https://svn.apache.org/repos/asf/camel/trunk/components/camel-jpa/src/test/java/org/apache/camel/examples/

For example

https://svn.apache.org/repos/asf/camel/trunk/components/camel-jpa/src/test/java/org/apache/camel/examples/MultiSteps.java

[rajk1000]

Hi there,

Many thanks for the swift reply. This all works fine.

I am experiencing a situation , however, whereby, the code runs through fine the @Consumed methods are called, which update the entity. This actually persists when I look at the results in the DB at the end of the execution flow.

However, when I run the same code effectively, through my test code, using mvn test, to run, the test results are all asserted positively, and the test passes, showing that the updates that the @COnsumed method was supposed to make, did indeed take place. So all good! However, when I look in the DB afterwards, I find that these fields in teh table were'nt actually updated!

I am extending the  'org.apache.camel.ContextTestSupport' class as part of my test. Is there any concept of this test class automatically rolling back any changes that were made. I remember ome Spring Test classes having this functionality for Unit Testing, thus meaning that one doesn't have to 'clean up' the database afterwards.

Sorry, I realise I haven't described in much detail here, but I just wonder if any form of automatic rollback is done in any of the Test classes, similar to the Spring Test class I was talking about..

Or any other ideas on what may be going on here?