o more problems with lost database connection
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jpa-and-PersistenceException-tp5795205p5798255.html
Sent from the Camel - Users mailing list archive at Nabble.com.
reported.
I haven't worked out a good unit test strategy for this but I have a couple
of ideas using an embedded hsqldb.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jpa-and-PersistenceException-tp5795205p5795841.html
Sent from the Camel - Users mailing list archive
, then it seems reasonable to do something like
this.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jpa-and-PersistenceException-tp5795205p5795550.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ut I'm not on solid ground
> yet in determining how the EntityManager is supposed to react under these
> circumstances. It seems like the locally stored EntityManager just doesn't
> give up this bad connection.
>
>
>
>
>
>
> --
> View this message in context:
>
ike the locally stored EntityManager just doesn't
give up this bad connection.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jpa-and-PersistenceException-tp5795205.html
Sent from the Camel - Users mailing list archive at Nabble.com.