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 381F5100B3 for ; Wed, 13 Nov 2013 09:59:02 +0000 (UTC) Received: (qmail 1687 invoked by uid 500); 13 Nov 2013 09:58:36 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 1516 invoked by uid 500); 13 Nov 2013 09:58:30 -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 1410 invoked by uid 99); 13 Nov 2013 09:57:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Nov 2013 09:57:53 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com designates 209.85.223.174 as permitted sender) Received: from [209.85.223.174] (HELO mail-ie0-f174.google.com) (209.85.223.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Nov 2013 09:57:48 +0000 Received: by mail-ie0-f174.google.com with SMTP id ar20so185830iec.5 for ; Wed, 13 Nov 2013 01:57:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=WlJzxzYYLz0FXu6qeW+agyrWVL4B2xlsa5D+Q78LurE=; b=uOy7PFiSmU4+xIeFc1r6TotDK+CvMrrzfI4spvXnzmAv8mk5wsI6FDhMQuQNmILf7B bB6BK41Cjvx2kn9wfOLYEjT8Sqnb0ONBiS4f5cU48ZSlRtKS7PC7XGWusDzO/f6cQY9h Hg0Ux3CDGAICiqGi5eHNW/4M9j+4WGjl7EDRAbGYo31fEqUwXxfyWHzggRCPpbwqABkI 2seOBai7zJiGxGn9GwDCXFW6bB65P4x+2HCSk/WXnLOvj6U2w3TLl8Y0PRMk5yDH9zCv JXlAgptCf0dXZc+2OiBRl7Km8QV2774sS8FZf0wq3h5PJXjMHWoSd++4a7n2iYWx2w5a JVrQ== X-Received: by 10.50.77.72 with SMTP id q8mr18369380igw.14.1384336647075; Wed, 13 Nov 2013 01:57:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.168.38 with HTTP; Wed, 13 Nov 2013 01:57:06 -0800 (PST) In-Reply-To: <1384336104990-5743165.post@n5.nabble.com> References: <1384336104990-5743165.post@n5.nabble.com> From: Claus Ibsen Date: Wed, 13 Nov 2013 10:57:06 +0100 Message-ID: Subject: Re: Composed Message Processor To: "users@camel.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Yeah the composed message processor can do that. In Camel you can use the splitter or multicast / recipient list which has built-in aggregation. for example from cxf multicast parallel aggregate strategy to a to b end On Wed, Nov 13, 2013 at 10:48 AM, bilalalp wrote: > Hi everyone, i have a question about composed message processor. I'm using > camel in an integration project. For a case , i need to use composed message > processor but i don't know where it is suitable or not. > > Here is the case: > > A web service request is coming and then i need to create two request from > this request. After the responses comes i need to create one response from > them then send it back. > > I think i can use Composed message processor but i'm confused. > > Camel in Action book says that every message has correlation identifier so > what about the web service requests? Do they have a special correlation keys > inside? > > Can i use this pattern for that situation? > > Best Regars. > > > > -- > View this message in context: http://camel.465427.n5.nabble.com/Composed-Message-Processor-tp5743165.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cibsen@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen