[
https://issues.apache.org/jira/browse/CAMEL-10000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307543#comment-15307543
]
John D. Ament commented on CAMEL-10000:
---------------------------------------
Hey guys, so I think I see the real issue, not hard to fix either.
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
As a result, the tests pass and say that OWB (1.2.x) should work. In
actuality, dropping a war with camel cdi on to Apache TomEE (1.7.4) doesn't
work, but dropping it on the newly released TomEE 7 does. 1.7 can't parse the
beans.xml file that is deployed. Seeing {{bean-discovery-mode}} in the
{{beans.xml}} file threw me off, as that's a clear CDI 1.1 feature. Same with
the scan tags. If the contents of the {{<scan/>}} tags are important, then no
it won't work in OWB.
> 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)
