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 12:33:30 +0000 (UTC)
From: "Werner Punz (Commented) (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Message-ID: 
 <1950001173.5499.1323779610764.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1295742340.15903.1297720437498.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MYFACES-3043) Ajax: response(...) function
 breaks if request(...) has not been called previously
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Werner Punz commented on MYFACES-3043:
--------------------------------------

I reopened the error egain with https://issues.apache.org/jira/browse/MYFACES-3401, I will add a regression test to my testsuite, so that it will never happen again.
                
> Ajax: response(...) function breaks if request(...) has not been called previously
> ----------------------------------------------------------------------------------
>
>                 Key: MYFACES-3043
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3043
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.4
>            Reporter: Nick Belaevski
>            Assignee: Werner Punz
>             Fix For: 2.0.5
>
>
> In RichFaces for file upload component we call jsf.ajax.response(...) method to process contents of IFRAME element. The problem is that this call is not preceded by call to jsf.ajax.request(...), making MyFaces fail:
> response : function(request, context) {
> this._q._curReq._response.processResponse(request, context);
> }
> this._q._curReq - is undefined.

--
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