Hello,
im using different types of lists ( e.g. selectmanymenu or selectonemenu) and in the past there was no problem if i select an empty value ( selectonemenu-> i used <f:selectItem itemLabel="" itemValue="#{null}"/>, for selectmanymenu with checkboxes it was enough to remove all picks) .
Today i noticed if i switch to a empty value, the component do nothing, it remains in his old state. After a page reload the picks are back. After debugging i noticed even the converter method wont be called after the empty pick. And if i use a form where is still a empty selectonemenu (with a converter), the buttons wont fire the action after pressing them.
I just update PrimeFaces from 6.1.7 to 6.2 and added PrimeFacesExtentions for the Timer.
Was there a big change in this update (Beside the using of PrimeFaces.current())?
Thanks!
Weird behavior with all list with use a converter
-
- PrimeFaces Core Developer
- Posts: 3979
- Joined: 03 Dec 2010, 14:11
- Location: Bavaria, DE
- Contact:
We have a migration guide https://github.com/primefaces/primeface ... tion-Guide
Everything else could be a bug. But please try with a source build before.
Everything else could be a bug. But please try with a source build before.
Thomas Andraschko
PrimeFaces | PrimeFaces Extensions
Apache Member | OpenWebBeans, DeltaSpike, MyFaces, BVal, TomEE
Sponsor me: https://github.com/sponsors/tandraschko
Blog: http://tandraschko.blogspot.de/
Twitter: https://twitter.com/TAndraschko
PrimeFaces | PrimeFaces Extensions
Apache Member | OpenWebBeans, DeltaSpike, MyFaces, BVal, TomEE
Sponsor me: https://github.com/sponsors/tandraschko
Blog: http://tandraschko.blogspot.de/
Twitter: https://twitter.com/TAndraschko
-
- Posts: 15
- Joined: 10 Feb 2017, 16:09
Nevermind, found my problem. Got a NullPointerExeption but was not showed in the console or somewhere else. Im using the setter of the value to set other values and forget to check if the given value is null or not. I know using the setter more then as a setter is not good, im trying to use this as minimal as possible.
Just weird this worked perfectly in 6.1 and just stopped in 6.2. Look like the ExceptionHandling was edited. (6.1 just ignored it and 6.2 stopped the code without a alert).
Just weird this worked perfectly in 6.1 and just stopped in 6.2. Look like the ExceptionHandling was edited. (6.1 just ignored it and 6.2 stopped the code without a alert).
using PF 11.0.4 / Tomcat v.7.0
-
- Information
-
Who is online
Users browsing this forum: No registered users and 40 guests