Not to beat a dead horse. But here's the thing. I am evaluating Sling for a project we're working on. I came to it ignorant about Sling and Jackrabbit and JSR170. So my initial thought was, hey this looks cool, nice shiny stuff. And so they use Jackrabbit cool, and a quick cursory look of the Jackrabbit project didn't scream out to me, Database needed. And while you can imagine that a Database would be cool and bring some important features, it's also not unreasonable to think that there might be some other persistence and storage system (XML & Lucene magic) happening at document insertion. Obviously while it is not the responsibility of the developers of Sling to call out all the possible configurations you could use with this software, it is reasonable to call out the stuff your using in your demos.
There is a big list of technologies listed on that page, Sling Components but no where is the persistence manager called out. That said here's what we need to do and you can tell me if you think Sling solution is appropriate and can be implemented in a short period of time. I have a workflow process external to the sling instance, running in a web app on glassfish. This instance manages the workflow associated with a document. After initial editing that moves to status Issued. Once in Issued it can follow one of three paths to completion of work flow. When the workflow moves to the Issued state, I want to insert an XML summary record into a content repository. As the document moves forward there are certain transitions that occur and each of those transitions has the potential to modify the summary. These are going to be represented by new versions of the XML and new versions of the XML document in the repository. The identifier for the document doesn't change only the contents change. I need a simple query page, that given one of several identifiers, can pull up either a list of summary documents and allow the users to choose one, or identify exactly one summary document. This document is then going to be rendered in HTML, for the user to view. There will be ldap authentication to restrict access to the repository. Placing documents in the repository should be as simple as the app on glassfish executing an HTTP Post operation, correct? Can the query page be done as a JSP inside of sling? Or should I just use Sling to server the results into another app? Tony Giaccone
