[
https://issues.apache.org/jira/browse/CAMEL-10000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307703#comment-15307703
]
Antonin Stefanutti commented on CAMEL-10000:
--------------------------------------------
{quote}
Yeah, the problem is that Weld 1.1 has a <scan/> element as well, which is what
became the CDI 1.1 <scan/>. So its not that Weld 1.1 is ignoring the XML, its
that it was already built to support it.
{quote}
It is generally _ignored_ or _supported_ :). OWB 1.2.7 is ignoring it and Weld
1.1 supports the {{<weld:scan>}} element, but that's the first time a
_validation_ error is reported, but it looks like OpenEJB is being zealous :).
{quote}
The first problem is that your tests don't actually leverage the beans.xml file
used in the production deployment. Here for instance:
https://github.com/apache/camel/blob/camel-2.17.x/components/camel-cdi/src/test/java/org/apache/camel/cdi/test/AdvisedRouteTest.java#L79
{quote}
These are _unit_ tests meant to test the Camel CDI features. We should add
_integration_ tests for the covered target containers to validate the (CDI
version x implementation x deployment type) combination matrix.
So, the new namespace information cannot be added as it breaks older Weld 1.x
compatibility. I presume we can change {{<beans version="1.0">}} to {{<beans
version="1.1">}} but that remains to be tested.
> Camel CDI incorrectly reports beans.xml version of 1.0
> ------------------------------------------------------
>
> Key: CAMEL-10000
> URL: https://issues.apache.org/jira/browse/CAMEL-10000
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.17.1
> Reporter: John D. Ament
> Assignee: John D. Ament
> Fix For: 2.17.2
>
>
> Camel CDI's beans.xml incorrectly reports version = 1.0 but should be 1.1 due
> to compatibility requirements.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
