[
https://issues.apache.org/jira/browse/MYFACES-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896186#comment-17896186
]
Markus Jung commented on MYFACES-4689:
--------------------------------------
not 100% sure on this: BV support tests if the impl is actually working so the
message looks fine to me, servlet 6.0 just checks if some new method is
available so also looks fine to me
> CDI support log message can be misleading
> -----------------------------------------
>
> Key: MYFACES-4689
> URL: https://issues.apache.org/jira/browse/MYFACES-4689
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 4.0.2
> Reporter: Markus Jung
> Priority: Minor
> Fix For: 5.0.0, 4.0.3, 4.1.0-RC4
>
>
> I was debugging something in Apache TomEE and was confused that I saw this in
> my logs
> {code:java}
> INFO - MyFaces Core CDI support enabled
> INFO - MyFaces Core Bean Validation support enabled
> INFO - Couldn't discover the current project stage, using Production
> INFO - MyFaces Core has started, it took [9206] ms.
> {code}
> I knew for sure CDI was not available in FacesInitializerImpl because that's
> the part I have been debugging. The log message depends on if
> jakarta.enterprise.inject.spi.BeanManager is available on the Classloader,
> not if a running CDI container was actually detected when MyFaces started
>
> IMO either the log message should be changed to something like "MyFaces Core
> successfully detected CDI" (which IMO can still confuse users) or the message
> should just be logged in FacesInitializerImpl
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
