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.