Is there a reason it can't be called before the message is routed, even if
its not guaranteed to finish before the message is routed?
Executing @Consumed functions is part of the stated functionality of the JPA
component. It seems logical that the work occurs while the message is still
at such a n
I've ran into a bit of odd behavior from the JPA component. I've configured a
JPA consumption route as follows:
from("jpa:com.models.MyRecord?consumeDelete=false&consumer.query=select r
from com.models.MyRecord r where r.batchID = NULL").to("direct:jpaOut");
The model contains the following updat
Was this camel-sardine component ever completed? If not, could you pass my
contact info on to the community member who was developing the component?
I need this component for a project I'm developing at work. I've spoken to
my boss and he is optimistic about the company permitting me to release th