jamesnetherton opened a new issue #3204:
URL: https://github.com/apache/camel-quarkus/issues/3204
To reproduce run `MinimalConfigTest` from the servlet extension deployment
module.
I see we are producing `AdditionalBeanBuildItem` for each servlet class
present in the servlet configuration. Is this actually necessary? I don't see
the benefit.
```
================================================================================
CDI: programmatic lookup problem detected
-----------------------------------------
At least one bean matched the required type and qualifiers but was marked as
unused and removed during build
Removed beans:
- CLASS bean [types=[class javax.servlet.http.HttpServlet, interface
org.apache.camel.http.common.HttpRegistryProvider, interface
javax.servlet.Servlet, class org.apache.camel.http.common.CamelServlet,
interface javax.servlet.ServletConfig, class javax.servlet.GenericServlet,
interface java.io.Serializable, class
org.apache.camel.component.servlet.CamelHttpTransportServlet], qualifiers=null]
Required type: class
org.apache.camel.component.servlet.CamelHttpTransportServlet
Required qualifiers: [@javax.enterprise.inject.Default()]
Solutions:
- Application developers can eliminate false positives via the
@Unremovable annotation
- Extensions can eliminate false positives via build items, e.g. using
the UnremovableBeanBuildItem
- See also https://quarkus.io/guides/cdi-reference#remove_unused_beans
- Enable the DEBUG log level to see the full stack trace to identify
the method that performed the lookup
================================================================================
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
