If the <camelContext> tag contains tags prefixed with the camel namespace, which is declared in the blueprint tag, the Route Editor complains that it doesn't know about the namespace. If the camel namespace is defined in the <camelContext> tag itself, everything is fine.

In the case of spring XML files, we seem to do the right thing... (although we do strip the "camel:" from the tag names when round-tripping between the source and design views...)

(The reason that the camel: tags are used in the first place is that without them, even with the proper namespace declaration, the Eclipse XML editor won't autocomplete tag names without using a prefix. See ECLIPSE-779 for more on this...)