You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Nils Lundquist (JIRA)" <de...@myfaces.apache.org> on 2012/10/15 20:30:03 UTC

[jira] [Commented] (MYFACES-2914) jsf.js spec broken by adding mojarra behavior

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

Nils Lundquist commented on MYFACES-2914:
-----------------------------------------

There is a regression or implementation error to this behaviour as noted in: https://issues.apache.org/jira/browse/MYFACES-3626
                
> jsf.js spec broken by adding mojarra behavior
> ---------------------------------------------
>
>                 Key: MYFACES-2914
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2914
>             Project: MyFaces Core
>          Issue Type: Bug
>            Reporter: Werner Punz
>            Priority: Minor
>             Fix For: 2.0.2
>
>
> We have a small 2.0reva spec violation by introducing a mojarra behavior.
> Mojarra appends always the issuing element in execute (not sure yet if it is also added if none is passed)
> The spec clearly states that if @none is passed in execute absolutely nothing is added to the execute list:
> Since 2.0 reva is a fairly new spec, I can savely assume this is the expected behavior.
> If the keyword @none is present, do not create and send the post data argument javax.faces.partial.execute.
> So in reality we have to check for none and do not create anything here

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira