Justin Edelson wrote: > The difference between Sling-Namespaces and what I need is that > Sling-Namespaces is static whereas I need dynamic behavior. Now if > NamespaceMapper was exported and extensible, that might do the trick. Ah ok, so what about exporting this service and maybe extending it to allow to add namespace mappings through API.
> SLING-1366 is a bit confusing to me because I use Sling-Namespaces and > haven't run into this, but that could be because all of the namespaces are > also in cnd files. I'll take a look at that later. Yes, if they are in a cnd file this will work already. The Sling-Namespaces support is just there to ensure that a prefix really points to the url you want it to in your application. So it's more a safety feature if people start reconfiguring their repository and the prefixes there. Carsten -- Carsten Ziegeler [email protected]
