[ https://issues.apache.org/jira/browse/MYFACES-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789195#comment-17789195 ]
Manuel K commented on MYFACES-4643: ----------------------------------- Thank you for your comment. That sounds logical. Are you saying that USE_CDI_FOR_ANNOTATION_SCANNING and OmniFaces are incompatible and that's okay? I would be fine disabling this feature, but as I wrote above it doesn't help. We get the same exception without this setting, but I can't reproduce it in primefaces-test. Do you have any idea how that could happen or how I should debug that? > OmniFaces converters not found using CDI > ---------------------------------------- > > Key: MYFACES-4643 > URL: https://issues.apache.org/jira/browse/MYFACES-4643 > Project: MyFaces Core > Issue Type: Bug > Components: General > Affects Versions: 4.0.1 > Reporter: Manuel K > Priority: Major > Attachments: primefaces-test.zip > > > [As I wrote in the OmniFaces GitHub > repository|https://github.com/omnifaces/omnifaces/issues/744#issuecomment-1824172540]: > 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: > {code:java} > jakarta.faces.FacesException: Could not find any registered converter-class > by converterId : omnifaces.SelectItemsConverter {code} > It especially happens when using the following context-param: > {code:java} > <context-param> > > <param-name>org.apache.myfaces.annotation.USE_CDI_FOR_ANNOTATION_SCANNING</param-name> > <param-value>true</param-value> > </context-param> {code} > 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. > -- This message was sent by Atlassian Jira (v8.20.10#820010)