Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
4.0.1
-
None
-
None
Description
As I wrote in the OmniFaces GitHub repository:
When upgrading from OmniFaces 4.1 to 4.2/4.3 in our application (WildFly 30, MyFaces 4.0.1), we get the following errors due to the change to the bean-discovery-mode discussed in the linked GitHub issue:
jakarta.faces.FacesException: Could not find any registered converter-class by converterId : omnifaces.SelectItemsConverter
It especially happens when using the following context-param:
<context-param>
<param-name>org.apache.myfaces.annotation.USE_CDI_FOR_ANNOTATION_SCANNING</param-name>
<param-value>true</param-value>
</context-param>
But in our application it even happens without it. Reproducer using primefaces-test is attached. Run it using mvn clean jetty:run -Pmyfaces40 and the exception appears.
I would have thought that it would be an OmniFaces issue, but melloware thinks it's a MyFaces issue.