Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Date: Tue, 13 Dec 2011 10:09:31 +0000 (UTC)
From: "Werner Punz (Commented) (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Message-ID: 
 <1620044864.5170.1323770971196.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <757140793.39337.1321553032122.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MYFACES-3401) Issue with RichFaces fileUpload
 component using MyFaces 2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MYFACES-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168276#comment-13168276 ] 

Werner Punz commented on MYFACES-3401:
--------------------------------------

Ok we still have an error in the codebase, even if we interprete the stack narrow a context:{source:{id="bla"}} should go through because all our _mfInternal values are purely optional. Now we are getting an error in that case.
This needs to be fixed and we probably also once this is fixed can deal with the context:{} case for richfaces 4.0 easily, no matter what the result is. a context:{} simply probably should response the xml but should skip the viewstate application on the origin elements form, according to the logic of the code. In case of richfaces 4.0 the viewstate application is not needed because it is not altered during the fileupload anyway (richfaces intercepts the request processes the multipart request drops the file into a temp dir and then once done pushes a another ajax request over the normal lifecycle to process the rest of the ajax handling.

                
> Issue with RichFaces fileUpload component using MyFaces 2.0
> -----------------------------------------------------------
>
>                 Key: MYFACES-3401
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3401
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.9
>            Reporter: Paul Nicolucci
>            Assignee: Werner Punz
>         Attachments: webapp.war
>
>
> I have an application that I'll attach to this issue that can reproduce this issue.  To reproduce you need to: 
> 1) Install webapp.war
> 2) navigate to index.xhtml
> 3) click the "add" button and select a file to upload ( any file it does not matter )
> 4) click the "upload" button
> The following error occurs: context.source is undefined  -> jsf.js.jsf:6422
> If I look at the jsf.js line 6422 I see the following:
>    var elementId = (context._mfInternal)? context._mfInternal["_mfSourceControlId"] : context.source.id;
> The above line is in the processUpdate : function(request, context, node)  method.  I'm not very familiar with the JS within MyFaces so I wanted to open up an issue and get some feedback from the community.
> I see that other issues have been opened regarding RichFaces fileUpload such as : https://issues.apache.org/jira/browse/MYFACES-3043

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira