<p:ajax> not working on Glassfish 3.1.2 to 4.12 migration

UI Components for JSF
Post Reply
alex2018
Posts: 4
Joined: 17 Jul 2018, 23:18

17 Jul 2018, 23:47

Hi,

Currently there is a JSF 2.0 web-application using Primefaces 3.5 that runs properly in Oracle Glassfish 3.1.2 (on JDK 1.7, Java EE 6).
All I need is migrate this application to be able to run it on Oracle Glassfish 4.1.2 - which is Java EE 7. \
I read the JEE 7 spec and it referred to JSF 2.2. The JSF 2.2 spec states that it provides backward compatibility for JSF 2.0, 2.1, all you have is leaving the namespaces to jsf 2.0 namespaces in faces-config.xml.
For the migration I changed the project configuration(Maven managed) as follows:
- changed the dependency from Java EE 6 api to Java EE 7 api
- changed the dependency "org.glassfish.main.extras:glassfish-embedded-all" from 3.1.2.2 to 4.1.2
- built it with JDK 1.7 or JDK 1.8

The problem is that: <p:ajax > invocations do not work:
- if there is a listener setup it is not fired at all (I checked with breakpoints, logs)
- I have some radiobuttons and when I press one I disable the others and enable a textimput(through a presentation model variable). Checked again with the debugger and neither of these gets called following pressing the button.
If I replace <p:ajax> with JSF component <f:ajax> the events get propagated just fine. Only that it's not feasible everywhere and it's too much work to do.

My question is: what am I doing wrong in this migration setup? Should I use other versions of the frameworks?
I only want to make the application run on Oracle GF 4.1.2.

Thanks in advance

kukeltje
Expert Member
Posts: 9605
Joined: 17 Jun 2010, 13:34
Location: Netherlands

18 Jul 2018, 14:38

Can you make a http://stackoverflow.com/help/mcve? Impossible to say what might be causing this

Post Reply

Return to “PrimeFaces”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 56 guests