Felix Meschberger wrote: > Hi, > > Am Montag, den 10.12.2007, 12:28 +0100 schrieb Carsten Ziegeler: >>> In the Sling jcr/resource implementation we will have this mapping >>> support and we may introduce such a helper for example as a request >>> attribute or on-demand through a factory method of the >>> JcrResourceManagerFactoryImpl (to be renamed of course to >>> JcrResourceResolverFactoryImpl) as >>> >>> ObjectMapper getObjectMapper(Session session); >>> >>> microsling has no object mapping and thus no such feature. >>> >>> WDYT ? >>> >> Hmm, yes makes sense - would it be possible to make the ObjectMapper >> available through the ServiceLocator? I think that's a little bit more >> convenient than storing it into an request attribute. > > I agree regarding the request attribute (therefore I prefer the new > JcrResourceManagerFactory method). We cannot register the ObjectMapper > as a service because it will most certainly be linked to a Session, > which is available per session. > Yes (and I fear sooner or later we have to find a solution for this as well). As a summary: this means that services that are tied to the current request like the ObjectMapper are available through the ServiceLocator (which is tied to the current request as well); but these services including the ServiceLocator are not registered as OSGi services.
Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
