I am getting a few hundred of these in my log. I have found and read the
following post <https://groups.google.com/g/ops4j/c/NC6V4YgEdis> from 2015
but that is not really answering the question.
First it would be great to update the log message to provide some context
like:
log.warn("failed to parse and instantiate of
javax.servlet.ServletContainerInitializer ({}) in classpath of context
bundle {}", className, bundle);
But I seem to be having issue with a couple of cases. A few dealing with
Atmosphere and most from
ch.qos.logback.classic.servlet.LogbackServletContainerInitializer. When
looking at the bundle, those bundles are not even aware of logback and will
not find the class, and it's not visible to the server bundle either. More
than likely that bundle is transitively reachable, but that doesn't imply
downstream visibility, which is what is required for the bundle or server
bundle to load the class.
I'm not sure at that point why that would trigger a warning and or why we
would want to apply our search transitively in the first place, but I might
be missing some obvious use cases.
Thanks for enlightening me.
Cheers,
Alain
--
--
------------------
OPS4J - http://www.ops4j.org - [email protected]
---
You received this message because you are subscribed to the Google Groups
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ops4j/e9436f50-0e74-473c-a9bc-02b9e35a845dn%40googlegroups.com.
