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

Werner Punz edited comment on MYFACES-4710 at 2/25/25 7:58 AM:
---------------------------------------------------------------

here is a prototype of a working version:

!image-2025-02-24-21-50-18-216.png|width=530,height=241!

as you can see the o object is passed in as params into the options of the ab 
call

The output is accordingly  
!image-2025-02-24-21-51-24-014.png|width=595,height=78!

so this needs to be fixed on the java side for the renderer which emits the 
call, I can do this tomorrow evening, but if anyone wants to take over this, 
feel free. I will roll a new release of the scripts as time permits which fixes 
the events issue (this needs some tests on my side)

--- 

hold off with the fixing for another day I need to look into some things first, 
maybe I have to alter the ab function slightly (which is just an appreviation 
for the jsf.ajax.request call anyway, I introduce it to be closer to mojarra 
with its ab call). This has nothing to do with the issue however, the issue is 
valid that the parameters are lost one way or the other by not passing them 
into the ab call properly!

 

 

 


was (Author: werpu):
here is a prototype of a working version:

!image-2025-02-24-21-50-18-216.png|width=530,height=241!

as you can see the o object is passed in as params into the options of the ab 
call

The output is accordingly  
!image-2025-02-24-21-51-24-014.png|width=595,height=78!

so this needs to be fixed on the java side for the renderer which emits the 
call, I can do this tomorrow evening, but if anyone wants to take over this, 
feel free. I will roll a new release of the scripts as time permits which fixes 
the events issue (this needs some tests on my side)

--- 

hold off with the fixing for another day I need to look into some things first, 
maybe I have to alter the ab function slightly (which is just an appreviation 
for the jsf.ajax.request call anyway, I introduce it to be closer to mojarra 
with its ab call)

 

 

> 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, image-2025-02-24-21-21-16-189.png, 
> image-2025-02-24-21-50-18-216.png, image-2025-02-24-21-51-24-014.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)

Reply via email to