Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2A9D418796 for ; Fri, 24 Jul 2015 14:28:50 +0000 (UTC) Received: (qmail 44706 invoked by uid 500); 24 Jul 2015 14:28:49 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 44659 invoked by uid 500); 24 Jul 2015 14:28:49 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 44647 invoked by uid 99); 24 Jul 2015 14:28:49 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2015 14:28:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 193E71A77B9 for ; Fri, 24 Jul 2015 14:28:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id dDj99mu9tCV9 for ; Fri, 24 Jul 2015 14:28:43 +0000 (UTC) Received: from mail-la0-f52.google.com (mail-la0-f52.google.com [209.85.215.52]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 683D843DD9 for ; Fri, 24 Jul 2015 14:28:43 +0000 (UTC) Received: by lagw2 with SMTP id w2so15173125lag.3 for ; Fri, 24 Jul 2015 07:27:51 -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=ShHimzKuAror/ysrCH1Jk53GRjn6/+wp9zpbZyHAs/Y=; b=dfBd5G0ADCErcF6Cs8AwsX70Je4Iy4eriHwyUCWyQpp15EhCDRpjC2P4nKq8v2meVL BkhibcmOfh2mLCk1YAILPcfqVlUj9+lvIYR4sAPVjZRxy0XhxUcQlw+k3dS91tAHhlLI /7Z16FOteBTKjdrDVwzch5PxlbEroAf0aEnmE1n353CBgS6jFOePOu4B5SleWQSS7tuu 97i/b7TzHOBZhRlWGWUrV8ixO/gMyJWnapMvb/xMp/7GgyIGH3JAyJzeXkZJHYBy9kYG iLjlSU7X3sjVIz6vpd+yKNuT5YmM+GbnbIFZ/u7SMOT1L5iSNJKrMHrsQ+luJLsky+yh 4Euw== MIME-Version: 1.0 X-Received: by 10.112.105.104 with SMTP id gl8mr14085708lbb.81.1437748071349; Fri, 24 Jul 2015 07:27:51 -0700 (PDT) Received: by 10.25.24.79 with HTTP; Fri, 24 Jul 2015 07:27:51 -0700 (PDT) In-Reply-To: References: Date: Fri, 24 Jul 2015 16:27:51 +0200 Message-ID: Subject: Re: To CXF experts: Setting of SOAP headers via the Camel Header "org.apache.cxf.headers.Header.list" for CXF data format "PAYLOAD" From: Aki Yoshida To: "dev@camel.apache.org" Content-Type: text/plain; charset=UTF-8 Hi Franz, I wanted to look at this but had not had time and a little late to comment. One question or concern that I had wasthat this would change the behavior of the existing tunneling scenarios using some soap headers, no? In other other words, some unwanted headers might tunnel through and show up at the other end? thanks. regards, aki 2015-07-21 12:44 GMT+02:00 Franz Paul Forsthofer : > Hi, > > can I assume that there are no objections against the patch I proposed > in https://issues.apache.org/jira/browse/CAMEL-8978? > > Best Regards Franz > > On Fri, Jul 17, 2015 at 10:02 AM, Franz Paul Forsthofer > wrote: >> Hi, >> >> Accessing the SOAP headers via the Camel header >> "org.apache.cxf.headers.Header.list" after a CXF consumer works fine, >> also for the CXF data format "PAYLOAD". >> >> However, currently the setting of SOAP headers via the Camel header >> "org.apache.cxf.headers.Header.list" is not working for a CXF producer >> with CXF data format "PAYLOAD". >> >> I found out that the list value contained in Camel header >> "org.apache.cxf.headers.Header.list" is correctly forwarded to the >> CXF request, however in the CxfEndpoint.CamelCxfClientImpl this list >> is overwritten by the value CxfPaylaod.getHeaders(). >> >> Therefore I propose to merge the values from the Camel header >> "org.apache.cxf.headers.Header.list" with the values of >> CxfPaylaod.getHeaders(). This has the advantage that you can set the >> headers either via the CxfPayload or by the Camel header >> "org.apache.cxf.headers.Header.list". >> >> For more details have a look at https://issues.apache.org/jira/browse/CAMEL-8978 >> >> Can somebody of the CXF experts comment whether my solution is >> feasible. Then I will commit the patch. >> >> Best Regards >> >> Franz Forsthofer