Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9F452DAEE for ; Fri, 3 Aug 2012 22:16:28 +0000 (UTC) Received: (qmail 36619 invoked by uid 500); 3 Aug 2012 22:16:27 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 36592 invoked by uid 500); 3 Aug 2012 22:16:27 -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 36583 invoked by uid 99); 3 Aug 2012 22:16:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Aug 2012 22:16:27 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com designates 209.85.216.173 as permitted sender) Received: from [209.85.216.173] (HELO mail-qc0-f173.google.com) (209.85.216.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Aug 2012 22:16:21 +0000 Received: by qcab12 with SMTP id b12so904553qca.32 for ; Fri, 03 Aug 2012 15:16:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=bEJCQTmtvoTsmT24/R+EPlSF6JIrVHv81r9bH292/6A=; b=QBgJeqvcoeSsrKqdb3J5INny2H6HiGwngEKpF1N+KT6I9sh4HP06Hw1hWl+9MG6v3r w7bEvRRDwyX78UQIgE+cT0udCJLg5IIZDcZY2QpDKrwH/sEOwzgLUJ6gk92HcDTYUMuk Tv7FnVuyoklU0kJEECK0VLRyEJAQStBCJRl+fx1xCGvSTwfDBkYRMXz3720+LtnbCJN7 PUGY2YnuS0xUxnxovoOnDHBWweShngh7n+eOjkelAijLmUIiCKaoBIO1eg4Sj8UQY9Ve mkYxiv3kQSj+wPL4o6k1ietk4sbziX1N/MNVb2ZqFDhquB7ClR7CjQKQg4jqTrJzAKYd PVig== MIME-Version: 1.0 Received: by 10.224.52.205 with SMTP id j13mr5251191qag.62.1344032160258; Fri, 03 Aug 2012 15:16:00 -0700 (PDT) Received: by 10.49.48.97 with HTTP; Fri, 3 Aug 2012 15:16:00 -0700 (PDT) In-Reply-To: <1343981157147-5716755.post@n5.nabble.com> References: <1343981157147-5716755.post@n5.nabble.com> Date: Sat, 4 Aug 2012 00:16:00 +0200 Message-ID: Subject: Re: camel-cache questions From: =?ISO-8859-1?Q?Christian_M=FCller?= To: users@camel.apache.org Content-Type: multipart/alternative; boundary=20cf3074b1e27a991c04c663df29 --20cf3074b1e27a991c04c663df29 Content-Type: text/plain; charset=ISO-8859-1 This should help: http://camel.apache.org/content-enricher.html Best, Christian On Fri, Aug 3, 2012 at 10:05 AM, helander wrote: > Hi, > > first of all, I guess that a cache instance is accessable from components > in the same VM, i.e. not bounded to a specific camel context or route? > > By big question is related to the following scenario: > > I have a set of CXF Endpoints and associated routes. At the end of the > routes, a request/reply to a JMS destination is performed. As part of > processing along the routes, I need to use data that is stored in an LDAP > server. I want to cache this data in order to avoid an LDAP server > round-trip on each request. > > I would be most grateful, if someone could provide an outline of how this > could be done, preferably using Spring/Blueprint DSL, but Java DSL would be > fine to (I could probably "translate"). > > One thing that I wonder about is that, as I understand it, somehow need to > create an additional exchange to interact with the LDAP server, and how you > would "fork" a new exchange and "join" back to the original exchange when > the LDAP data has been returned, is mystery to me at the moment. > > Thanks > > Lars > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-cache-questions-tp5716755.html > Sent from the Camel - Users mailing list archive at Nabble.com. > --20cf3074b1e27a991c04c663df29--