Hi Preben,
yes. There is indeed an option. By default it is set to auto which seems
to cause the commit.
The problem is that we need the uncommitted data to do the query.
Interestingly outside of OSGi in spring it seems to behave differently.
There the data seems to go to the first level
Seems our analysis was wrong. Camel is not involved in the problem after
all.
It seems to be a problem with hibnernate doing a commit before a
criteria based lookup.
Christian
On 05.11.2014 16:23, Christian Schneider wrote:
I have an application running in OSGi that uses aries blueprint
I have seen that before in the old ejb days.
The trick is to tell the persistent provider not to do commit before query.
I would guess that Hibernate has a option to turn commit before query off.
Preben
--
View this message in context:
I have an application running in OSGi that uses aries blueprint and
aries jpa.
My class A is marked as transactional in blueprint and uses an XA
transaction.
Inside such a transactional method from class A I
- first create a persistent entity in the DB
- then call a camel route using