Hello,

Michael Oliver wrote:

[Mike Oliver>>] While it is possible to extend the slide servlet and
even add JSP pages to the slide servlet container to build a web based
html application to do that, I would not. I would build a Struts
Application and use the Slide Client Library to talk to Slide. Why?
Because the forms you are talking about likely include multiple
properties and Slide is atomic in its property management, so using the
Client Library to do PROPPATCH on the properties of your forms will be
much cleaner.


What should I do in order to search the database in order to get the list of files containing some text entered as a query? I consider I should use a WebDAV's SEARCH method, but this is through the DAV protocol. I want to develop a web form, the user can enter query into it, and then he or she gets the results of the query in a simple web page. [Mike Oliver>>] Again the slide servlet could be extended but I would do
it with a Struts Application and use the Slide Client Library behind
your actions.


I thought of such solution, but didn't know it is the right way to do it.

Is there a posibility to provide a functionality to allow the user to click on a resource in order to edit and _save_ the file back into the repository?
[Mike Oliver>>] Huh? You should learn more about WebDAV because that is
exactly what you do in a WebFolder or from a Microsoft Office
application accessing Slide.


Don't ou laugh. I just could not imagine how to show to the user a form when he or she is saving a document into the repository. Maybe I don't know all features of MS Office or OpenOffice.org (both supporting WebDAV). Uploading therefore should look like this for example:
Client (browser) requests a web page /upload.do in order to handle the upload. When it is called without parameters it forwards to the form, when the user enters properties and selects the document to upload. Then the form calls again /upload.do - now with parameters (properties and the file itself). Action servlet handles the request, forms WebDAV request using client software and makes the request saving the described file into the repository. It is clear - correct me if I am wrong.
The second thing is searching: done for example by /search.do action. It gets the query string from parameters, prepares DAV request and using client library for WebDAV calls the respository - gets in return list of files that match the query, produces then HTML page containing the results. It is clear also (I think I am right).
But wen we e.g. open a file from this result list by clicking, edit it into MS Office or OOo and try to save it back into the repository - how could the action servlet that handles the update action show the form to fill the properties in again? I don't understand that :( Does MS Office or OOo support special forms generated from some - let's say - "template" got from server to be filled when saving files into the repository? Or maybe there is a posibility to force open the form just after saving the file? And the last thing: how our action servlet can handle the DAV request and produce HTML forms in the same time?


Thanks for the answers. :)

--
Greetings,                       --== registered linux user #230042 ==--
Pawel Garbacz <[EMAIL PROTECTED]>    --== ICQ 111972667 :: GG 2532007 ==--


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to