[
https://issues.apache.org/jira/browse/CXF-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669242#comment-15669242
]
ASF GitHub Bot commented on CXF-7133:
-------------------------------------
Github user johnament commented on a diff in the pull request:
https://github.com/apache/cxf/pull/199#discussion_r88162864
--- Diff: integration/cdi/src/main/resources/META-INF/beans.xml ---
@@ -2,7 +2,4 @@
<beans xmlns="http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://jboss.org/schema/cdi/beans_1_1.xsd";>
- <scan>
--- End diff --
Having this config here makes shaded JARs hard to deal with in CXF. CDI
has this feature built in to ignore the bean, which works better IMHO.
> Don't rely on disabled scanning in CDI
> --------------------------------------
>
> Key: CXF-7133
> URL: https://issues.apache.org/jira/browse/CXF-7133
> Project: CXF
> Issue Type: Bug
> Components: Integration
> Affects Versions: 3.1.9
> Reporter: John D. Ament
> Fix For: 3.1.9
>
>
> In CXF-7097, a scan tag was added to turn off default application scanning.
> This approach doesn't work for all packaging types, and creates a bit of an
> issue informing consumers.
> Would be better if the class were just written correctly to not be discovered.
> I have a patch, will raise after the other one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
