camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David J. M. Karlsen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CAMEL-7461) Idempotent inconsistensies / idempotent consumer should allow for messageId of any type
Date Fri, 23 May 2014 07:50:01 GMT
David J. M. Karlsen created CAMEL-7461:
------------------------------------------

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


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)

Mime
View raw message