Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 67418 invoked from network); 16 Jun 2010 06:38:52 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Jun 2010 06:38:52 -0000 Received: (qmail 61472 invoked by uid 500); 16 Jun 2010 06:38:52 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 60725 invoked by uid 500); 16 Jun 2010 06:38:49 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 60711 invoked by uid 99); 16 Jun 2010 06:38:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jun 2010 06:38:48 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [194.25.187.90] (HELO mailgw-2.ptv.de) (194.25.187.90) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jun 2010 06:38:41 +0000 X-ASG-Debug-ID: 1276670297-632f00b70000-Zj7sc6 X-Barracuda-URL: http://172.23.97.112:8000/cgi-bin/mark.cgi Received: from ska-wn-e30.ptvag.ptv.de (localhost [127.0.0.1]) by mailgw-2.ptv.de (Spam & Virus Firewall) with ESMTP id 43FEBEC3FB6 for ; Wed, 16 Jun 2010 08:38:17 +0200 (CEST) Received: from ska-wn-e30.ptvag.ptv.de ([172.23.67.23]) by mailgw-2.ptv.de with ESMTP id HdjzSvyK0gHyPZey for ; Wed, 16 Jun 2010 08:38:17 +0200 (CEST) X-Barracuda-Envelope-From: Max.Ullinger@ptv.de X-ASG-Whitelist: Client Received: from SKA-WN-E25CEX.ptvag.ptv.de ([172.23.66.200]) by ska-wn-e30.ptvag.ptv.de ([172.23.67.23]) with mapi; Wed, 16 Jun 2010 08:38:16 +0200 From: Max Ullinger X-Barracuda-BBL-IP: 172.23.66.200 X-Barracuda-RBL-IP: 172.23.66.200 To: "users@camel.apache.org" Date: Wed, 16 Jun 2010 08:38:18 +0200 X-ASG-Orig-Subj: AW: Routing new data from a DB query, updates from JMS Subject: AW: Routing new data from a DB query, updates from JMS Thread-Topic: Routing new data from a DB query, updates from JMS Thread-Index: AcsMpe9rrSyXNh/OQQCwm11JzJua2wAeEVsg Message-ID: <8BD008FC9041C04FAD36A0BD46AAA69D010134AB00@SKA-WN-E25CEX.ptvag.ptv.de> References: <28893315.post@talk.nabble.com> In-Reply-To: <28893315.post@talk.nabble.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: UNKNOWN[172.23.67.23] X-Barracuda-Start-Time: 1276670297 X-Barracuda-Virus-Scanned: by MailGW-2 at ptv.de X-Virus-Checked: Checked by ClamAV on apache.org Hi 1) Camel has components for JPA, SQL etc. why can't you use them fort he da= tabase query? 2) JMS. Perfect with Camel If your problem is accessing both data sources in the same route look at th= e "Aggregator" EIP or the "Enrich" EIP, I think they can serve as a kind of= "join" of several datasources into one route. Cheers, Max -----Urspr=FCngliche Nachricht----- Von: Gsegel [mailto:gsegelken@itsfac.com]=20 Gesendet: Dienstag, 15. Juni 2010 18:15 An: users@camel.apache.org Betreff: Routing new data from a DB query, updates from JMS A quick rundown of our situation...Our system operates in a very dynamic environment where accessing the data to route will have to be done in two 'phases': =20 1. Perform an initial query to a database(s) and route any new records=20 2. Listen for updates pushed to a JMS Queue and route I have the book and have been reading as much as I can but I can't figure out how the functionality of querying for new data should best be handled.= =20 One thought is to have a component (outside of Camel) that queries for data and pushes to a JMS Queue...at that point Camel could take it from there (using the JMS Queue as a 'from' in a route). My other thought is to integrate this query logic in a Camel route but I get really lost when I think of the best way to do it. =20 Maybe I could use a JPA component to get new data and at the same time have a route that pulls from a JMS Queue? It seems that Camel is exactly what we need for the routing/filtering capabilities but I'm having serious problems in figuring out how to get the data to the Camel infrastructure. Any help/advice would be greatly appreciated! --=20 View this message in context: http://old.nabble.com/Routing-new-data-from-a= -DB-query%2C-updates-from-JMS-tp28893315p28893315.html Sent from the Camel - Users mailing list archive at Nabble.com.