> The key point here is that the services jclouds-karaf provides, have to be > "named". And the ChefApi and ChefService alone don't have a name.
That's what I understood too, based on your description (thanks!). I should start by saying that I'm fine with the change as-is and I don't want to spend more of your time on this than necessary, but for me the real question then is: does it make _sense_ for either the ChefApi or the ChefService to be named, or not? If not, then I agree that creating a `NamedChefApi` decorator simply to make Karaf happy is probably more messing than caching the context directly, even though it currently feels to me a bit that we're caching "the first object we can find that has a name" ;-) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/65#issuecomment-99301693
