>> >If the sub service name is not set, the service reg property is not set, >the >target is then target="(!(subServiceName=*))"
Carsten, you are suggesting that is mapping.subServiceName == null then I should not put the property in the service reg. I added a property with empty string but I can do it as you suggest and drop the property altogether if it is null. On a slightly related topic, looking more closely to the ServiceUserMapperImpl I see that there are several levels of fallback for service user resolution (fallback to bundle default, or to global default). While this offers a lot of flexibility, to me it feels a bit strange in the context of a security feature. If defaults are set, it can happen (especially at startup) that code is executed using different serviceUsers, e.g. a component can execute using the bundle default or global default until its specific subService is available, and it can be easily imagined how this can cause subtle errors. Marius
