>* API: I suggest to break this out of the Sling API bundle into a separate >bundle. One of the problems I see we have with the API bundle is that is >becoming more and more a collection of API with independent lifecycle. >Particularly the Resource API has its own life warranting its own bundle. >But this type conversion is another one. (And yes I know we also have a >packaging problem in the API bundle, which might have to be fixed)
yes, i see this point problem: ValueMapDecorator *is* part of the API. if we move the conversion logic to a new bundle Sling API needs to depend on it. unless we deprecate ValueMapDecorator in the API and move it somewhere else. currently API has not dependencies except javax.servlet and slf4j-api. stefan
