I have not done anything similar to do this but I have worked quite a bit on
Camel. So here are my thoughts -

I do not see anything wrong with the approach, instead of writing to table
and than writing it off to another JMS queue, you can make use of
ibatis/hibernate component and realize the table itself as queue. Basically
you can ask camel hibernate component to delete entry from table when it is
consumed and than route that message to any other component as you would
like.

Thanks!



Pitre, Russell wrote:
> 
> Hi-
> 
>  
> 
> I just discovered Camel and I am very excited to start working with it!
> 
> 
>  
> 
> Since I'm just starting out I don't know the lay of Camel land yet and
> would like to solicit feedback on my integration solution using Camel.
> Ultimately what I want to do is generate an event when a record is
> inserted into a MS SQL Server 2000 database. 
> 
>  
> 
> These db records are inserted from a closed source thick client that I
> have no way of integrating with and kick off a few manual business
> processes that we would like to streamline.  The only way I see to
> generate an event is to write an INSERT Trigger to insert a
> corresponding record into a queue table.  I would then have a Camel
> route that contains a 'timer' and  'bean' component to look at the queue
> table, send a message to an ActiveMQ queue, mark the queue table record
> as processed and be done.  We would then setup a camel route for each of
> the additional business processes that we want to streamline.
> 
>  
> 
> I realize it's not a sexy solution, but it's simple and will get the job
> done considering I'm not working with integration friendly technologies.
> 
>  
> 
> Is anyone else doing something similar or have any comments (good or
> bad)?
> 
>  
> 
> Thanks for your input
> 
>  
> 
> -Russ
> 
>  
> 
>  
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Newbie-looking-for-feedback-on-generating-events-from-a-database-insert-tp25752447p25773503.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to