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.
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. 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? BR, Juanjo. [1] https://issues.apache.org/jira/browse/SLING-254
