Problem solved. The issue was that even though the documentation
states that JPA consumer must specify the entitytype, I found that it
worked without it and I never got an explanation *why* it was needed.
Since I already had a big, giant URI, I left it out. Apparently one
of the reasons the JPA consumer needs it, is support for the
"@Consumed" mechanism, which I found out by debugging. Now that I put
it back, my "@Consumed" handler works...
On Mon, Feb 25, 2013 at 11:56 AM, Chris Wolf <cwolf.a...@gmail.com> wrote:
> I have a route whose first endpoint is .from("jpa:...) - i.e. a
> consumer. I have consumeDelete=false and in my entities, I have a
> method
> marked with "@Consumed" - in this method, I invoke another setter to
> set a nullable persistent field of type DATE. Everything works,
> but this date field is still null. When I run in the debugger, the
> method marked by @Consumed never gets invoked.
>
> How/what detects this "@Consumed" annotation?
>
> Thanks,
>
> -Chris
