[
https://issues.apache.org/jira/browse/CAMEL-7461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108949#comment-14108949
]
Claus Ibsen commented on CAMEL-7461:
------------------------------------
Its a bit tricky as users would need to configure the type and make sure it
matches the implementation of the repo etc. And also potential an API change.
As String is a generic type the impl can just support that type too, if it uses
integers etc.
> Idempotent inconsistensies / idempotent consumer should allow for messageId
> of any type
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-7461
> URL: https://issues.apache.org/jira/browse/CAMEL-7461
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.13.1
> Reporter: David J. M. Karlsen
> Priority: Minor
> Fix For: Future
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
