Robert Munteanu wrote > On Tue, 2017-05-09 at 09:41 +0200, Oliver Lietz wrote: >>> There is the assumption that if such a mapping is available the >>> underlying service user is available as well - which unfortunately >>> is >>> wrong. In this sense we could also remove the whole concept again >>> and >>> simply assume that if the JCR resource provider is available, the >>> service user is created. It's the same shaky assumption but just >>> simpler :) >> >> AFAIR (I'm on holidays and have no time to check) the mapping is >> registered >> only when the service/system user is present. I had problems in >> integration >> tests where system users materialized after service user mapping >> config was >> processed and they failed. > > Looking at the code I don't see this happening. >
I don't think so either - if you wait for the mapping configuration by having a dependency your component might be activated later which by chance solves the problem. But there is no guarantee atm Regards Carsten > I agree that we should make it work properly. > > Robert > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
