[
https://issues.apache.org/activemq/browse/CAMEL-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62433#action_62433
]
Claus Ibsen commented on CAMEL-3178:
------------------------------------
@Hadrian
Thanks for advice.
That community already have a ticket about publishing their own product into
their own maven repo. So that said community is aware of the need.
The fusesource repo is an alternative if they do not rise to the occasion.
> Db4o component
> --------------
>
> Key: CAMEL-3178
> URL: https://issues.apache.org/activemq/browse/CAMEL-3178
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: Henryk Konsek
> Assignee: Claus Ibsen
> Priority: Trivial
> Fix For: 2.5.0
>
> Attachments: db4o_component.patch, db4o_wiki.txt
>
>
> I had to perform some Hibernate to Db4o (http://www.db4o.com) integration
> task. I needed to monitor SQL database for inserts, process them and save to
> the NoSQL Db4o store for further processing. I achieved that with Hibernate
> component (http://camel.apache.org/hibernate.html) and my custom Spring-Bean
> objects accessing db4o.
> However I think that if we already got Hibernate support in Camel, it would
> be nice to provide similar component for db4o. I extracted core logic from my
> Db4o Spring Bean and created Db4o component from it. I'm attaching patch with
> the code (patch to Camel-Extra since db4o is licensed on *GPL).
> This is basic yet usable version of db4o component. It is much simpler than
> Spring Bean I used to resolve my Hibernate->Db4o issue. No advanced
> configuration, no complex customization. Just core idea extracted from it. If
> you think that Camel can make use of this db4o component and add it to the
> codebase, then I can make it more configurable and flexible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
