Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 77464 invoked from network); 17 Dec 2010 06:24:26 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Dec 2010 06:24:26 -0000 Received: (qmail 38719 invoked by uid 500); 17 Dec 2010 06:24:26 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 38682 invoked by uid 500); 17 Dec 2010 06:24:26 -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 38674 invoked by uid 500); 17 Dec 2010 06:24:25 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 38671 invoked by uid 99); 17 Dec 2010 06:24:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Dec 2010 06:24:25 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Dec 2010 06:24:23 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oBH6O1co021900 for ; Fri, 17 Dec 2010 06:24:01 GMT Message-ID: <6491015.172681292567041688.JavaMail.jira@thor> Date: Fri, 17 Dec 2010 01:24:01 -0500 (EST) From: "Claus Ibsen (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Commented: (CAMEL-3429) Extend DSL with more header filtering constructs In-Reply-To: <26839216.126071292371569509.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CAMEL-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972367#action_12972367 ] Claus Ibsen commented on CAMEL-3429: ------------------------------------ To keep backward compatible we could introduce a 2nd parameter for the exceptions * {{removeHeaders(pattern, exceptionsPattern)}} remove one or more headers based on a pattern, skipping any which has been defined as exceptions. So if you just want to remove all headers, exception foo, then you can do, {{removeHeader(null, "foo")}} or maybe more readable {{removeHeaders("*", "foo")}} Then in the JAXB model the exceptions is just another attribute, so its compatible {code:xml} {code} > Extend DSL with more header filtering constructs > ------------------------------------------------ > > Key: CAMEL-3429 > URL: https://issues.apache.org/jira/browse/CAMEL-3429 > Project: Camel > Issue Type: Improvement > Components: camel-core > Affects Versions: 2.5.0 > Reporter: Richard Kettelerij > Fix For: Future > > Attachments: remove-headers-camel-core.patch > > > Currently the DSL offers the following methods: > - {{removeHeader(name)}} which removes a single header > - {{removeHeaders(pattern)}} remove one or more headers based on a pattern (since 2.3) > The attached patch extends the DSL with the following methods: > - {{removeHeaders(name...)}} removes the headers in the given a vararg parameter. > - {{removeHeadersExcept(pattern)}} removes all headers except for the ones matching the given pattern (opposite of {{removeHeaders(pattern)}}) > - {{removeHeadersExcept(name...)}} removes all headers except for the ones in the given vararg parameter (opposite of {{removeHeaders(name)}}) > The rationale for the removeHeadersExcept() method is that in many cases you want to take a _defensive_ approach with regard to header propagation. > Sometimes you may want to remove _every_ header on the current message, in that case just call removeHeadersExcept() with no arguments. > In other cases you want to propagate only the "id" header received through the servlet/jetty component (as a query parameter). In that case call > removeHeadersExcept("id") to preserve the "id" header, while preventing other query parameters (and standard HTTP headers) to flow down your route. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.