[CAMEL-7461] Idempotent inconsistensies / idempotent consumer should allow for messageId of any type

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 2.13.1
• Fix Version/s: Future
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: David J. M. Karlsen
• Created: 23/May/14 07:49
• Updated: 29/Mar/18 11:30
• Resolved: 29/Mar/18 11:30

Description

See http://camel.465427.n5.nabble.com/Idempotent-inconsistencies-td5751484.html for a background.

Basically there is inconsistency between a idempotent consumer and the repository. The repository is capable of holding any type, while the consumer is non-parameterized and uses String as it's message type.

It would be very handy to have the messageid as a domain type for any application, and thus the consumer should allow for a parameterized type T.

This will also probably mean that JpaMessageIdRepository should allow for any persistent type.

If doing this camel would be generic on the type, and allow for supporting application domain types w/o customizations.

Issue Links

• is related to: CAMEL-10098 AbstractJdbcMessageIdRepository<T> is not actually parameterizable