Primefaces dropdowns and fields cannot be set to empty post migrating to Jboss EAP 7.2.8GA
-
- Posts: 3
- Joined: 23 May 2022, 15:37
We are currently running PrimeFaces 6.1 and Primefaces 6.1 extensions for our application. Below is the pom.xml for the versions used. We have migrated from Linux version 6 running wildfly 10.1.1 Final to Linux version 7 running Jboss EAP 7.2.8 GA. We have also migrated from Oracle 12c to Oracle 19c. Post the migration of our same code dropdowns, fields that can be kept empty or non selected cannot go back to this state. So if there is a value present we can change the vale to some other value but it cannot be saved as empty. Also the dropdowns do not set to the first "Please select option". This is weird as the same code works fine in the previous old environment.
Without example code and a PrimeFaces Test reproducer we have no idea what you are doing or how to possibly help you.
PrimeFaces Developer | PrimeFaces Extensions Developer
GitHub Profile: https://github.com/melloware
PrimeFaces Elite 13.0.0 / PF Extensions 13.0.0
PrimeReact 9.6.1
GitHub Profile: https://github.com/melloware
PrimeFaces Elite 13.0.0 / PF Extensions 13.0.0
PrimeReact 9.6.1
-
- Posts: 11
- Joined: 07 Mar 2019, 15:20
Agree this needs a Test reproducer.
My guess it could be:
- missing JDK_JAVA_OPTIONS org.apache.el.parser.COERCE_TO_ZERO=false
- missing context-param INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL
- difference between default mojarra jsf versions wildfly 10 vs boss EAP 7
- difference in JDK
- ... (anything else)
My guess it could be:
- missing JDK_JAVA_OPTIONS org.apache.el.parser.COERCE_TO_ZERO=false
- missing context-param INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL
- difference between default mojarra jsf versions wildfly 10 vs boss EAP 7
- difference in JDK
- ... (anything else)
-
- Posts: 3
- Joined: 23 May 2022, 15:37
Below is a sample of our code which was working fine in the old version of Jboss (wildfly 10.1.1 Final) but post migrating the dropdown if set to some value will not reset back to "Select Sku" option. It just resets back to the last value that was chosen. I even removed " noSelectionOption="true" and " itemDisabled="#{refSku.activeFlag.toString() == 0}" and added itemValue="" and itemValue="${null}"... None of them seemed to work... Th
Dropdown example:-
<p:column headerText="Sku #" width="15%" sortBy="#{testSkuData.skuCode}" id="skuCodeId">
<p:selectOneMenu
styleClass="shortestSelectMenuStyle"
panelStyleClass="shortestSelectMenuStyle"
value="#{testSkuData.skuValue}" effect="none">
<f:selectItem
itemLabel="Select Sku" noSelectionOption="true"/>
<f:selectItems
value="#{testDataBean.testSkuNumber}"
var="testSku"
itemLabel="#{testSku.value}"
itemValue="#{testSku.value}"
itemDisabled="#{testSku.activeFlag.toString() == 0}"/>
<p:ajax event="change" listener="#{cellEditHandler.updateSKUInfo(testSkuData)}"
resetValues="true" update="testSkuTable"
onstart="PF('testSkuBlocking').block();"
onsuccess="PF('testSkuBlocking').unblock();"/>
</p:selectOneMenu>
Date field snippet:-
<p:row>
<p:column styleClass="#{skuRowStyle}">
<p:outputLabel value="Predicted"/>
</p:column>
<p:column styleClass="#{skuRowStyle}">
<h:outputText value="#{testData.predictedtestDate}"
rendered="#{testData.testSku}">
<f:convertDateTime pattern="dd-MMM-yyyy"/>
</h:outputText>
<p:calendar size="10" id="predictedtestDate"
pattern="dd-MMM-yyyy"
value="#{testData.predictedtestDate}"
navigator="true" style="font-size:10px"
rendered="#{not testData.testSku}">
<p:ajax event="dateSelect"
listener="#{testDatesHandler.handlePredictedtestDate}"
update="date1field, date2field,date3field"/>
<p:ajax event="keyup"
listener="#{testDatesHandler.handlePredictedtestDate}"
update="date1field, date2field,date3field"/>
</p:calendar>
<p:watermark value="Select Date" for="predictedtestDate"
rendered="#{not testData.testSku}"/>
</p:column>
</p:row>
-
- Posts: 3
- Joined: 23 May 2022, 15:37
DazzlingBob wrote: ↑24 May 2022, 15:22Agree this needs a Test reproducer.
My guess it could be:
- missing JDK_JAVA_OPTIONS org.apache.el.parser.COERCE_TO_ZERO=false
- missing context-param INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL
- difference between default mojarra jsf versions wildfly 10 vs boss EAP 7
- difference in JDK
- ... (anything else)
Below are the details:-
- missing JDK_JAVA_OPTIONS org.apache.el.parser.COERCE_TO_ZERO=false Not sure where to set this
- missing context-param INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL Already present
- difference between default mojarra jsf versions wildfly 10 vs boss EAP 7 jsf-impl-2.2.13.SP1(wildfly) and jsf-impl-2.3.5.SP2-redhat-00001(EAP)
- difference in JDK Oracle JDK 1.8.0_131 & OpenJDK 1.8.0_332
Just create a small reproducer using PrimeFaces Test: https://github.com/primefaces/primefaces-test
it is simply to create a minimum reproducible example.
it is simply to create a minimum reproducible example.
PrimeFaces Developer | PrimeFaces Extensions Developer
GitHub Profile: https://github.com/melloware
PrimeFaces Elite 13.0.0 / PF Extensions 13.0.0
PrimeReact 9.6.1
GitHub Profile: https://github.com/melloware
PrimeFaces Elite 13.0.0 / PF Extensions 13.0.0
PrimeReact 9.6.1
-
- Information
-
Who is online
Users browsing this forum: No registered users and 50 guests