Return-Path: X-Original-To: apmail-myfaces-users-archive@www.apache.org Delivered-To: apmail-myfaces-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 487B510E73 for ; Tue, 25 Feb 2014 15:20:57 +0000 (UTC) Received: (qmail 44890 invoked by uid 500); 25 Feb 2014 15:20:55 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 44727 invoked by uid 500); 25 Feb 2014 15:20:48 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 44664 invoked by uid 99); 25 Feb 2014 15:20:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Feb 2014 15:20:45 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of smithh032772@gmail.com designates 209.85.212.169 as permitted sender) Received: from [209.85.212.169] (HELO mail-wi0-f169.google.com) (209.85.212.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Feb 2014 15:20:39 +0000 Received: by mail-wi0-f169.google.com with SMTP id e4so4465821wiv.2 for ; Tue, 25 Feb 2014 07:20:19 -0800 (PST) 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=bHGsZvaXLE8exSvMMjo0nzIo+FfVkp02pAcV+vlRGYk=; b=LYXvBylBblynXo9Bkj3Lc66o5LBg21EMBkZO+X8+w/Zn7a7wb4Ecc9S1ieWTL0yk1e K9WqLXLWG0f7L4PLJ/mmUcUCHgIuiPTSZb4f7vcN2tKGIUljCWtAZ8SQu8o8AmJsa5v2 x5oHBwtW/J8WI/bCdYCl9qLjwVBDHmx6yhjNUrnSWZKJhpr9jEiwa1vUbrPPHQUXTdId LY/F64Sd0AqPtis073m5FPpvkvV9S2Uu+HsTy6nmkwIbnMDtpD8zsjXcEIM+zKGVEKj3 oqV8qSrowC8es2Qgig8RrvBus1pLYseWRMCChx2BzHMlqpmYBjdZYMVdajU7p3+SpEgE 58wA== MIME-Version: 1.0 X-Received: by 10.194.95.195 with SMTP id dm3mr1090550wjb.17.1393341619024; Tue, 25 Feb 2014 07:20:19 -0800 (PST) Received: by 10.227.221.81 with HTTP; Tue, 25 Feb 2014 07:20:18 -0800 (PST) In-Reply-To: References: Date: Tue, 25 Feb 2014 10:20:18 -0500 Message-ID: Subject: Re: 2.2.0 and multipart From: "Howard W. Smith, Jr." To: MyFaces Discussion Content-Type: multipart/alternative; boundary=047d7beb9b8040b98604f33ca0b0 X-Virus-Checked: Checked by ClamAV on apache.org --047d7beb9b8040b98604f33ca0b0 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 25, 2014 at 3:20 AM, Werner Punz wrote: > Am 22.02.14 02:58, schrieb Leonardo K. Shikida: > > Hi >> >> Just noticed this thread about tomee, myfacs 2.2.0 and multipart request >> >> stackoverflow.com/questions/21948228/how-to-get-jsf-file- >> upload-to-work-on-tomee-1-6 >> >> does anyone know if between 2.1.13 and 2.2.0, multipart request has got >> any >> new bug? could not find anything in JIRA >> >> the guy who posted the stackoverflow question tested with >> >> h:commandButton while I've reproduced the problem just switching >> myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using >> p:fileUpload >> >> [] >> >> Leo >> >> Hi this could be a new bug, we introduced a fileupload handling with JSF > 2.2 (the h:inputFile tag) maybe the normal multipart request handling was > broken by the extensions done in this area the best bet is to file a > bugreport in the myfaces bugtracker https://issues.apache.org/ > jira/browse/MYFACES > > Werner > > > +1 thanks Leonardo for informing the user list about this issue. I am using MyFaces 2.2 (and/via TomEE 1.6.1 snapshot) with my JSF web application, and I confirmed this bug/issue too in my app. PrimeFaces 4.x (simple) fileUpload is no longer working. :( maybe, it can/should be confirmed if MyFaces 2.2 (basic/simple) fileUpload works as designed/expected. i have not tested that though/yet. --047d7beb9b8040b98604f33ca0b0--