Yes. That's my interpretation of the specification too. Though in practice, implementations chose to implement the bean types as well (even if it's not required by the specification) as you mention. And that it especially true in that use case, that is a lookup by name only (made by Camel), i.e., with requested bean type Object, which would return a pretty useless client proxy if they would take the specification literally.

I'll try to find a work-around at the level of Camel. Still, the switch to chose to return a proxy that implements the requested type and the bean interfaces is a bit aggressive. Why not excluding the non proxyable types only. So in my case, the proxy would implement PropertiesComponent but not UriEndpointComponent?