I agree, it sounds like Sling will work for what you need. Personally I first was interested in using the JCR, and after learning that, Sling was very easy to pick up. I would definitely recommend getting some sort of JCR explorer so you can get a feel of how a jcr repository works, looks and feels. There are open source projects or you can use Day's developer product. I've never tried it, but from what I've ready by default you should be able to connect to a sling repo via jcr explorer using rmi://localhost:1099/jackrabbit.
For your use, keep in mind that in sling you don't have to use the default post handler. You can create a custom POST.jsp that will handle the post request however you want. All you need to do is set the parent's resource type. -----Original Message----- From: Bertrand Delacretaz [mailto:[email protected]] Sent: Friday, July 08, 2011 10:35 AM To: [email protected] Subject: Re: Beginners question with Sling. Hi Phil, On Fri, Jul 8, 2011 at 4:15 PM, Phil Rice <[email protected]> wrote: > ...Although I came to Sling for the Restful interface, there are a few of > features that Sling adds to Jackrabbit that I like: > 1: It looks as though Sling would deal with the schema changing across > time issue: The support for multiple renderers, and for those > renderers to be quite sophisticated looks as though I can ask for > resource.oldVersion0, resource.oldVersion1 or resource.json, and have > the correct values presented to me. > 2: I hope to be able to use the Sling rendering to reduce the chatter > between client and server... IMO this matches the general philosophy of Sling very well, so it looks like it's worth for you to hang in there! -Bertrand
