Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <22606876.33341291146855403.JavaMail.jira@thor>
Date: Tue, 30 Nov 2010 14:54:15 -0500 (EST)
From: "Hadrian Zbarcea (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Work started: (CAMEL-3379) Custom multipart parsing filter
 in camel-jetty
In-Reply-To: <17030619.8711291061230884.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-3379 started by Hadrian Zbarcea.

> Custom multipart parsing filter in camel-jetty
> ----------------------------------------------
>
>                 Key: CAMEL-3379
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3379
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jetty
>    Affects Versions: 2.5.0
>            Reporter: Paul Mietz Egli
>            Assignee: Hadrian Zbarcea
>         Attachments: camel-3379-custom-multipart-filter.diff, MultiPartFormTestWithCustomFilter.java
>
>
> After spending my holiday weekend trying to get the Jetty MultipartFilter class to work properly in our application, I finally gave up and modified a local build of camel-jetty so we could use our own multipart filter implementation in place of the standard one.  This seemed generally useful, so here's a patch against trunk if you would like to put it in.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.