[
https://issues.apache.org/activemq/browse/CAMEL-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea updated CAMEL-390:
----------------------------------
Assignee: Hadrian Zbarcea
Fix Version/s: 2.0.0
(was: 1.5.0)
I am not sure this is a valid issue yet. I suspect the xml is not correct but
I only have briefly looked into it. If I understand correctly this is related
to the use of refs.
It's ok for the xml doc to have one default namespace and than one element
(<camelContext>) to redefine the default namespace to be something else.
However, since we are dealing with qnames, the camelContext element should
define a different namespace mapping (and a prefix) for the default namespace
of the document (the spring namespace) and use that to qualify the element it
refs, so that resolution can happen.
But then again, I may have misunderstood the issue completely. I'll look into
it soon though.
> if folks overload xmlns to use camel, then define beans with <bean ...> Camel
> should generate an error with a useful error message
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-390
> URL: https://issues.apache.org/activemq/browse/CAMEL-390
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Assignee: Hadrian Zbarcea
> Priority: Critical
> Fix For: 2.0.0
>
>
> See this thread...
> http://www.nabble.com/BeanFactoryAware-%28Spring%29-tp16122107s22882p16124218.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
