Contribution of JdbcMessageIdRepository

[Christian Müller <ch...@gmail.com>]

Hello!

Because we had some problems setting up the JpaMessageIdRepository in our
FUSE ESB, I developed the JdbcMessageIdRepository, based on Springs
JdbcTemplate and similar to the JpaMessageIdRepository (ant I think it's a
more light-wight solution to persist two attributes instead of a full blown
ORM mapper...).
I would like to contribute this peace of code (and of course the unit tests
;o) ). I wonder, what the best place is for this peace of code. I think
camel-spring or camel-sql, because camel-jdbc doesn't have a dependency to
spring at present. Any suggestions?

Christian

Re: Contribution of JdbcMessageIdRepository

[Claus Ibsen <cl...@gmail.com>]

Hi

In fact we got this new camel-jdbc-aggregator. We could consider
moving that into camel-sql as well.
Then we have all pieces in the same component for JDBC using spring
JdbcTemplate.



On Wed, Feb 9, 2011 at 9:12 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Christian
>
> On Wed, Feb 9, 2011 at 9:01 AM, Christian Müller
> <ch...@gmail.com> wrote:
>> Hello!
>>
>> Because we had some problems setting up the JpaMessageIdRepository in our
>> FUSE ESB, I developed the JdbcMessageIdRepository, based on Springs
>> JdbcTemplate and similar to the JpaMessageIdRepository (ant I think it's a
>> more light-wight solution to persist two attributes instead of a full blown
>> ORM mapper...).
>
> Yeah often ORM is overkill. Think twice before going down that path.
>
>> I would like to contribute this peace of code (and of course the unit tests
>> ;o) ). I wonder, what the best place is for this peace of code. I think
>> camel-spring or camel-sql, because camel-jdbc doesn't have a dependency to
>> spring at present. Any suggestions?
>>
>
> I assume its the repo for the idempotent consumer EIP, eg IdempotentRepository
>
> Yeah I think camel-sql would be the best home as its for using the
> spring-jdbc, eg the Spring JdbcTemplate.
> So I would suggest camel-sql.
>
> If you put it in camel-spring, then that adds a dep on spring-jdbc,
> which we really dont want.
>
>
>
>
>> Christian
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Re: Contribution of JdbcMessageIdRepository

[Claus Ibsen <cl...@gmail.com>]

Hi Christian

On Wed, Feb 9, 2011 at 9:01 AM, Christian Müller
<ch...@gmail.com> wrote:
> Hello!
>
> Because we had some problems setting up the JpaMessageIdRepository in our
> FUSE ESB, I developed the JdbcMessageIdRepository, based on Springs
> JdbcTemplate and similar to the JpaMessageIdRepository (ant I think it's a
> more light-wight solution to persist two attributes instead of a full blown
> ORM mapper...).

Yeah often ORM is overkill. Think twice before going down that path.

> I would like to contribute this peace of code (and of course the unit tests
> ;o) ). I wonder, what the best place is for this peace of code. I think
> camel-spring or camel-sql, because camel-jdbc doesn't have a dependency to
> spring at present. Any suggestions?
>

I assume its the repo for the idempotent consumer EIP, eg IdempotentRepository

Yeah I think camel-sql would be the best home as its for using the
spring-jdbc, eg the Spring JdbcTemplate.
So I would suggest camel-sql.

If you put it in camel-spring, then that adds a dep on spring-jdbc,
which we really dont want.




> Christian
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/