Hey all,

Seeing as it is now best practice to not use the getAdminResourceResolver 
anymore but go for the getServiceResourceResolver, what is the best way to have 
a bundle on it's own create the service user that belongs to the bundle. I know 
you can put the 
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-mybundle.xml
 in the SLING-INF folder, but this only creates the mapping of the service user 
for your bundle, not the actual user. I have seen some mails about the repo 
init interface, but if I understand this correctly then that interface is fired 
on startup and before the jcr repository is live as osgi service. What then 
when you want to install a bundle that creates a service user for itself after 
the instance is already live?

Greetings,
Roy

Reply via email to