You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Leonard Lu (JIRA)" <ji...@apache.org> on 2010/04/12 23:24:49 UTC

[jira] Issue Comment Edited: (TAP5-722) Tapestry ajax form swallows server-side errors

    [ https://issues.apache.org/jira/browse/TAP5-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856181#action_12856181 ] 

Leonard Lu edited comment on TAP5-722 at 4/12/10 5:23 PM:
----------------------------------------------------------

Is this issue fixed by revision 924025 (http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/tapestry.js?r1=922440&r2=924025) for issue TAP5-863?

      was (Author: lwlu98):
    Is this issue fixed by revision 924025 (http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/tapestry.js?r1=922440&r2=924025) for issue TAP5-863 (https://issues.apache.org/jira/browse/TAP5-863)?
  
> Tapestry ajax form swallows server-side errors
> ----------------------------------------------
>
>                 Key: TAP5-722
>                 URL: https://issues.apache.org/jira/browse/TAP5-722
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Ciaran Wood
>         Attachments: TAP-722.patch
>
>
> I've encountered a bug in T5.1.0.5 where a form that submits via ajax (i.e.
> The form has its zone parameter set) will never notify the user if the
> server-side action fails. I've traced it down to this line in tapestry.js:
> // Set a default failure handler if none is provided.
> options.onFailure |= Tapestry.ajaxFailureHandler;
> This line is in the sendAjaxRequest function that gets added to all form
> elements via Prototype's Element.addMethods function. I used firebug to
> debug the above statement and instead of the OR assignment that it looks
> like, options.onFailure actually ends up being assigned the value '0'. I
> guess this means that its only a bitwise operation and can't be used for
> functions etc.

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