Sling Models Custom Injector Precedence Order
I have created a custom Sling Models injector. It's deployed as an OSGi service and works successfully but I have a problem.
The immediate question I have relates to the precedence order in which the injectors are called. I set my injector to have service ranking of 9999 so that it would likely only be called if I declared it explicitly with the @Source annotation, or so I thought. In reality it gets called for ALLmethods/fields unless I set them explicitly too e.g. to stop my custom injector being called I may set @Source("valuemap"). I suspect this is because my injector isn't registered properly or the configuration is awry. Obviously I'd like to ONLY have to specify my injector for those methods/fields that need it and leave all others to follow the default behavior, but I don't know how to do that.
Can someone help ?
Regards
Fraser