camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-6194) Create @PreConsumed Annotation or Fix @Consumed Annotation For JPA Component
Date Thu, 21 Mar 2013 15:49:15 GMT


Claus Ibsen commented on CAMEL-6194:

Matt sounds good.

You can read on this page about how to contribute patches

For example attaching a .patch file to this JIRA ticket.

Or if you are a github person, then there is some notes on that link as well.

The patch should be against the "trunk". As we accept new code on the trunk. And backport
bug fixes etc to older branches on a case by case basis.

> 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
>   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