Taking discussion to the list.... The primary use case is to support the Jackrabbit Server bundle which currently looks at the sling.home framework property with what I think is too much code in the JR bundle.
I agree that the repository should be the primary holder of state. I'm not sure that bundle data will work for something like Jackrabbit or another embedded repository. IIUC, the location of the bundle data directory is based on bundle ID, which seems to fragile - uninstalling and reinstalling the JR bundle shouldn't result in a fresh repository. Justin On Jun 23, 2011, at 4:29 AM, "Carsten Ziegeler (JIRA)" <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/SLING-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053707#comment-13053707 > ] > > Carsten Ziegeler commented on SLING-2089: > ----------------------------------------- > > What's the use case for this? I think we should encourage devs to not put > state into the file system directly :) > State should either go into the repo (or a Sling resource provider) or bundle > data should be used. > >> add a getAbsolutePath(String) method to SlingSettingsService >> ------------------------------------------------------------ >> >> Key: SLING-2089 >> URL: https://issues.apache.org/jira/browse/SLING-2089 >> Project: Sling >> Issue Type: Improvement >> Components: Extensions >> Reporter: Justin Edelson >> Assignee: Justin Edelson >> Fix For: Extensions Settings 1.0.4 >> >> >> We should encourage developers to put state under ${sling.home}. Although >> there's already a method which can get the sling home path, we can make it >> even easier by adding a method getAbsolutePath(String) in >> SlingSettingsService. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
