I've been working with Slide 2.0 source distribution for about 2 1/2 weeks now and still have not made the kind of progress I had hoped for. My goal is to integrate Slide into an existing Content Management Application and my plan has been to write a new Content Store(s) that makes API calls to the existing application for the ContentStore, RevisionDescriptorStore, etc methods. I've followed the advice found on the slide wiki "Get Your Arms Around It" http://wiki.apache.org/jakarta-slide/GetYourArmsAroundIt and have begun to get a better sense of what Slide is doing as it initializes and maps WebDAV requests to the domain configuration. However, I haven't made much progress past manipulating the returned NodeRevisionDescriptor object to change the display name, content size, etc.
There is a lot in Slide that the default TxXMLFileDescriptorsStore handles that I just don't need: Security, Locking, Permissioning, Versioning, etc. Many of these "features" already exist within my current Content Management Application. If I explain my current application's workflow and then what I hope to use Slide for, hopefully someone out there can help point me in the right direction. Currently, my Content Management Application allows users to create, edit, lock (etc) binary files like Word Docs, Excel SpreadSheets, Powerpoint presentations, and PDF's. The current process for editing an existing file has the user click on a link that retrieves the file from the service using standard HTTP GET. The user makes edits to the document and then saves to their local hard drive. To submit their changes, the user goes to a separate upload page, uses a HTML Form elements to "Browse" their local machine for the updated version and uploads back to the server. With WebDAV I am hoping to let users click on a link to edit a file which will open a Network Place through Win XP (No Problem). User opens Word Document by clicking on icon, makes changes, then saves back directly to the server through Word. So assume that each document version is already maintained within the Content Management application and uniquely identified. (like #12345). If I open a WebDAV client like Win XP Network Place to http://slideserver/slide/files/12345/ I simply want to be able to respond with the File name associated with that unique ID - after making API calls to see if doc 12345 exists, if the user making the request has access rights, etc. I don't need any of the information that is currently being maintained by the TxXMLFileDescriptorStore - its already in my existing Application. How can I "turn off" that part of slide (at least the initialization)? Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
