You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Paul Mietz Egli (JIRA)" <ji...@apache.org> on 2010/11/30 18:06:12 UTC

[jira] Issue Comment Edited: (CAMEL-3379) Custom multipart parsing filter in camel-jetty

    [ https://issues.apache.org/jira/browse/CAMEL-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965290#action_12965290 ] 

Paul Mietz Egli edited comment on CAMEL-3379 at 11/30/10 12:04 PM:
-------------------------------------------------------------------

Here's a unit test based on MultiPartFormTest which sets a custom filter and tests to see if that filter was used for processing.  

      was (Author: pegli):
    Here's a unit test based on MultiPartFormTest which sets a custom filter and tests to see if that filter was used for processing.  The patch 
  
> 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
>         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.