Primefaces: RequestContext.execute - Javascript called twice

Question

I'm using primefaces and have a problem executing JavaScript at the end of an ajax call. I add some action to the RequestContext, and it is executed twice!

RequestContext.getCurrentInstance().execute("alert('I'm here!')");

It is also embedded twice in the XML which I get back from the server - two times the same component and same node.

Primefaces Version is 5.3.10

Any ideas what is going wrong here? Thanks.

endDocument in PrimePartialResponseWriter is also called twice. It contains a call to encodeScripts which returns the nodes... — anm, Apr 15 '16 at 09:37
OK, it seems that it was a deployment-problem. We deployed it again and the problem is solved... — anm, Apr 18 '16 at 14:42
Then please either remove the question or create this as an answer — Kukeltje, Apr 18 '16 at 15:19
I have the same problem when calling the execute method from a p:commandButton. It doesn't happen when calling it in the @PostConstruct method. — Cenobyte321, Jul 25 '16 at 15:42
I have exactly same problem but after redeploy also problem not solved — Srikanth, Jan 19 '17 at 12:26

score 4 · Answer 1 · answered Jun 22 '17 at 16:12

It has been a while since last answer and problem seems to be solved but I believe I know what is going on and the reason new deployment solved the problem.

It seems it happens when you have more than one primefaces*.jar inside EAR (i.e. EAR/lib and WAR/WEB-INF/lib.

If anyone else is facing this problem, try to remove from EAR/lib (or EAR root), keep only one primefaces*.jar in EAR.

score 0 · Answer 2 · answered Feb 12 '18 at 10:52

0

I avoided such error by changing version of Primefaces from 6.0 to 6.1 in POM. (6.1 version was in libs of server Payara)

answered Feb 12 '18 at 10:52

Виталий Пугач

11

So effectively you also made sure there is just one PrimeFaces version? But which is used? – Kukeltje Feb 12 '18 at 12:34

score -4 · Accepted Answer · answered Apr 20 '16 at 06:37

-4

OK, it seems that it was a deployment-problem. We deployed it again and the problem is solved...

answered Apr 20 '16 at 06:37

anm

545
3
17

Primefaces: RequestContext.execute - Javascript called twice

3 Answers3