[
https://issues.apache.org/jira/browse/MYFACES-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929903#comment-17929903
]
Werner Punz commented on MYFACES-4710:
--------------------------------------
But back to the main problem this could be related to the issue with the
command script broken, it looks like it, I will have a look at it, as for the
source element issue, I will fix it together with the rest, it turns out it is
rather easy to fix!
> CommandScript: Behaves differently than Mojarra
> -----------------------------------------------
>
> Key: MYFACES-4710
> URL: https://issues.apache.org/jira/browse/MYFACES-4710
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 4.0.2, 4.1.0
> Reporter: Melloware
> Assignee: Werner Punz
> Priority: Major
> Attachments: image-2025-02-03-11-04-43-114.png,
> image-2025-02-03-11-04-58-475.png, omnifaces-push-194.zip
>
>
> Original report: https://github.com/quarkiverse/quarkus-omnifaces/issues/194
> Basically if you pass a socket reponse message directly to a CommandScript
> its supposed to convert those params to Request Parameters.
> {code:xml}
> <h:commandScript name="wsUpdate" action="#{omniPushBean.complex()}"
> render="something"/>
> <o:socket channel='complex' onmessage="wsUpdate"/>
> {code}
> If the socket message was
> {code:javascript}
> {"event":"test","id":"48e496b2-1aa7-42ec-bd57-0832c966d8c7"}
> {code}
> It the `wsUpdate` command is supposed to send those as Request parameters and
> Mojarra does this but MyFaces does not.
> Mojarra:
> !image-2025-02-03-11-04-43-114.png!
> MyFaces:
> !image-2025-02-03-11-04-58-475.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
