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

Werner Punz edited comment on MYFACES-4719 at 6/10/25 7:46 PM:
---------------------------------------------------------------

the a b is indeed fixed by the Renderer... this is a bug in the script builder, 
I can see now a and b being sent properly with a blank in between!

However also a difference, the issuing element is not attached to the execute 
here! While in 4.x it is!

Behavior and partial however are set properly!, I need to look into the issuing 
element issue, that however is on the js side!


was (Author: werpu):
the a b is indeed fixed by the Renderer... this is a bug in the script builder, 
I can see now a and b being sent properly with a blank in between!

However also a difference, the issuing element is not attached to the execute 
here! While in 4.x it is!

 

> Missing Form Data in Faces 3.0
> ------------------------------
>
>                 Key: MYFACES-4719
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4719
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 3.0.3
>            Reporter: Volodymyr Siedlecki
>            Assignee: Werner Punz
>            Priority: Major
>         Attachments: CommandScript.war, image-2025-06-05-15-45-56-719.png, 
> image-2025-06-05-15-46-24-876.png
>
>
> While running out test suite on MyFaces 3.0.3-SNAPSHOT, we encountered some 
> failures in the ajax tests.
> It looks like the following two entries are not sent over when comparing the 
> same app to MyFaces 2.3: 
> {code:java}
> "jakarta.faces.behavior.event": "action",
> "jakarta.faces.partial.event": "click",{code}
> The app just adds a FacesMessage when the bean is invoked: 
> {code:java}
>     <h:commandScript name="submitFormScript" 
> action="#{commandScriptBean.submitForm}" render="@form" />
>     <h:messages/>{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to