Solved
Are there any drawbacks getting Session from ResourceResolver
Are there any gotchas getting session from ResourceResolver
Util code :
public static ResourceResolver getRR(org.apache.sling.api.resource.ResourceResolverFactory factory) {
ResourceResolver resolver = null;
Map<String, Object> param = new HashMap<>();
param.put(ResourceResolverFactory.SUBSERVICE, "subservicename");
try {
resolver = factory.getServiceResourceResolver(param);
} catch (LoginException e) {
log.error("Login Exception :{}", e.getMessage());
}
return resolver;
}
service code :
@3214626
private org.apache.sling.api.resource.ResourceResolverFactory rrFactory;
public void someMethod(){
try (ResourceResolver resolver = MyUtil.getRR(rrFactory)){
Session session = resolver.adaptTo(Session.class);
etc...
session.save();
}
is this session thread safe, do I have to watch for concurrency, etc... ?
