Thanks Carsten for the response. We had thought about the same approach but calculating the configuration every time using this way did not seem good to us and we happened to define a config node (for example config.xyz) and then used configadmin to pick this up. This seems easier to manage also since developer could easily find out configuration file and doesn't need to traverse so many configuration entries to first figure out which is for a tenant which he was looking for. This is working well so far however IMO Sling should have some support for this feature too. What do you say and I will open a Jira?
-- View this message in context: http://apache-sling.73963.n3.nabble.com/Configuration-support-for-multi-tenant-use-cases-tp4062451p4062517.html Sent from the Sling - Users mailing list archive at Nabble.com.
