Hi, On Tue, Dec 3, 2013 at 9:29 PM, ChadDavis <[email protected]> wrote: > ...1) is it even possible to stack sling on top of a repo that we are already > using directly in our application. If so, how might that look?...
If your existing content is outside of the Sling servlet resolver's search path (/libs and /apps by default, configurable), Sling won't care about it, so you could start by running Sling on top of your existing repository, and gradually move to Sling servlets and scripts for your application. Sling *should* work with a remote Jackrabbit repository accessed via davex, but there might be some limitations, that's not a configuration that we extensively test. > > ...2) Does Sling care about what type of content I'm using? In particularl, > I'm thinking of what the relationshipo between my application level doc > types and the fact that sling seems to use the much simpler resourceType, > with associated templates embodying the knowledge about the structure . . .. Not sure what you mean by "application level doc types" - if that means that you're using code to aggregate repository data to create documents, that could work by having Sling services call your aggregation code and use the results in request processing. Creating a ResourceProvider that makes your content available to the default Sling rendering mechanisms is relatively easy, especially if (maybe initially at least) that's read-only operations. The simplest example of that is at [1], docs at [2]. To start experimenting you might just define a Sling-friendly content structure with nodes that have a sling:resourceType property, point your request processing scripts or servlets to that and add properties to these nodes that help find your actual content. Or add the sling:resourceType properties in the right places and go from there. Hope this helps, and feel free to ask if you start experimenting! -Bertrand [1] http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/resourceprovider/ [2] http://sling.apache.org/documentation/the-sling-engine/resources.html
