camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt McCann (JIRA)" <>
Subject [jira] [Commented] (CAMEL-6194) Create @PreConsumed Annotation or Fix @Consumed Annotation For JPA Component
Date Wed, 10 Apr 2013 20:55:16 GMT


Matt McCann commented on CAMEL-6194:

Attached the right one this time. Spaced out and attached the old patch before.
> Create @PreConsumed Annotation or Fix @Consumed Annotation For JPA Component
> ----------------------------------------------------------------------------
>                 Key: CAMEL-6194
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jpa
>    Affects Versions: 2.10.4
>            Reporter: Matt McCann
>            Priority: Minor
>              Labels: features, newbie
>             Fix For: Future
>         Attachments: Added-Preconsumed-annotation.patch, Added-Preconsumed-annotation.patch,
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> @Consumed functions are not called until after an exchange has been routed out of the
JPA component. Executing @Consumed functions is part of the stated functionality of the JPA
component so it seems logical that the @Consumed function should be called as part of routing
an exchange, not after the exchange has been routed.
> If possible, I think it'd be preferable to modify the @Consumed behavior though [~davsclaus]
has suggested the possible creation of an @PreConsumed annotation.
> I'm happy to implement this ticket this weekend if I can get some consensus on which
path is preferred by the community. This would be my first patch on the project so I figure
I ought not to run off on my own.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message