[
https://issues.apache.org/jira/browse/OWB-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478792#comment-17478792
]
Romain Manni-Bucau commented on OWB-1400:
-----------------------------------------
[~jfreire] there is a single rule, the rule about file is that you will get the
class name in general (MyService.class for ex) so you must go up using the
class name and you will end in WEB-INF/classes so either we consider we scan
blindly or we go up of 2 more level to check if we exclude the full war, was my
point.
> "/tomcat" entry in "org.apache.webbeans.scanExclusionPaths" disables scanning
> on official tomcat docker image
> -------------------------------------------------------------------------------------------------------------
>
> Key: OWB-1400
> URL: https://issues.apache.org/jira/browse/OWB-1400
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.23
> Environment: docker image tomcat:8.5-jdk17-corretto
> Reporter: Jose Luis Freire
> Priority: Major
>
> When deploying an application in a tomcat docker image, the application is
> typically installed in "/usr/local/tomcat/webapps".
>
> The application libs will typically be located in
> "/usr/local/tomcat/webapps/ROOT/WEB-INF/lib".
> The "/tomcat" entry in the exclusion path results in all the application
> beans getting ignored if the jar files don't have the "META-INF/beans.xml"
> (which isn't required in the default setup).
>
> I propose changing "/tomcat" to "/tomcat/lib" to avoid this overreaching
> optimization.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
