search

jboss / mojarra

Fork of Mojarra
10 stars 41 forks source link

Wrong behaviour UIInput's component #71

Closed samsonovav closed 4 years ago

samsonovav commented 4 years ago

After upgrading to wildfly 19.1.0 my projects don't work as expected. I localized problem in javax.faces.component.UIInput from jboss-jsf-api_2.3_spec 3.0.0.SP02 in validate(FacesContext context) method. When the context parameter javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL set to true then the value from UIInput component is not set to null any more. Moreover, the setter method on backing bean is not called in this case. I write here because the https://github.com/jboss/jboss-jakarta-faces-api don't have the place for issues.

erickdeoliveiraleal commented 4 years ago

you might want to open the issue also in root project that is https://github.com/eclipse-ee4j/mojarra , this bug may related to the fix of this issue https://github.com/eclipse-ee4j/mojarra/issues/4550

scottmarlow commented 4 years ago

you might want to open the issue also in root project that is https://github.com/eclipse-ee4j/mojarra , this bug may related to the fix of this issue eclipse-ee4j/mojarra#4550

I agree, +100

scottmarlow commented 4 years ago

Also worth adding a link to the discussion forum as well, in case further notes are added there, link is.

samsonovav commented 4 years ago

Ok. Thanks. I submitted issue to https://github.com/eclipse-ee4j/mojarra/issues/4704

erickdeoliveiraleal commented 4 years ago

@soul2zimate

Hurz commented 4 years ago

The fix has caused a new misbehaviour: When rendering a composit component with a facet containing a required input field, its validation triggers even though the field isn't rendered.

I've attached a reproducer to its Mojarra bug ticket https://github.com/eclipse-ee4j/mojarra/issues/4704 .

soul2zimate commented 4 years ago

It's the same issue as described in https://github.com/eclipse-ee4j/mojarra/issues/4716, it was fixed in https://issues.redhat.com/browse/WFLY-13497