Hi Juanjo, Juanjo Vázquez schrieb: > Hi, > > Last days I have been thinking about to extend the features of Sling > embedded repository. The main reason for this is configuring it with another > persistent manager and customizing with my own login module and access > manager.
Good point. I have been thinking on this a while ago, but came to no conclusion :-( > > Obviously, I could modify the deployed repository.xml (copied by > SlingServerRepository) but I would prefer not have to do it. I´m using the > web launchpad. Makes sense. > > Until now, I have used my own repository instance registered with RMI and > linked in Sling thanks to "sling.repository.url" property [1]. This works > fine but I´m afraid that I´ll be reinventing the wheel because I´d be > comfortable with a customized embedded repository. > > Any ideas? We could add a property to sling.properties (also overwritable through web app init-param) which setting the URL to a repository.xml file. Thus you could include the repository.xml file in your web app or place it somewhere else together with the repository home. Currently the jcr/jackrabbit-server bundle contains an Activator class, which sets up the repository to be located inside sling.home and copying the repository.xml from the bundle to the sling.home folder. We might want to change this code to respect the repository home and configuration locations set in the sling.properties (or system properties or web app init-param) and only fall back to the old defaults if the properties are not set. You are of course welcome to implement and commit such a patch. WDYT ? Regards Felix > > BR, > > Juanjo. > > [1] https://issues.apache.org/jira/browse/SLING-254 >
