In my application, I'm more using the java api than the webdav features. For content management is suffisant.
For document management, it is another problem, webdav is very important.
Did you check the Slide lastest cvs code ? Webdav support is more important - compare to the version 1.16.
Anyway, same conclusion : jetspeed is good, Slide is good, OpenOffice is good. Only some integration is required to have a more complete solution.
Fletcher, Boyd C. J9C534 wrote:
The idea of building a Jetspeed based CMS using Slide would be an excellent idea once Slide fully supports WebDAV 1&2, DASL, DAV ACL, and DeltaV. If we combined Jetspeed, Slide, Lucene, some security logic, and the Java version of OpenOffice SDK (for MS Office document filtering) we would have a powerful and portable document management system that could complete with Documentum, FileNet, QuickPlace and Livelink for most people's uses. In the meantime, integrating jetspeed with the excellent java based webDAV server from Xythos (www.xythos.com) might accomplish people's CMS goals and at lower cost than some of the big commercial CMS/document management solutions.
Using Ekit for HTML editing sounds like a great idea. Perhaps we could convince the author to license it under Apache's license.
boyd
-----Original Message-----
From: Christophe Lombart [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 5:17 PM
To: Jetspeed Developers List
Subject: Re: CMS service
The main goal of Slide is accessing a CMS repository by using different ways :
* A webdav server implemented via a servlet. In this case, all webdav clients like Word or many others can access directly to the content for update.
* Some java components which provides a complete java API for accessing a repository. So, you can build a new jetspeed service which will use this API for making retrieve, update, ....
Slide version 2 will be based on new a java API standardisation (see http://www.jcp.org/en/jsr/detail?id=170).
Furthermore, Slide gives the possibility to store your content where you want (even in a legacy system). You need to write a specific store which can be seen as a driver. For me, it is the best candidate for a default cms implementation for jetspeed. Transaction, versionning, lock is supported and security component is flexible. For example with a small amount of code, you can intergrate the jetspeed security model into Slide security model.
I'm agree, Slide vocation is to store the content and not edit it. So, we still need some very simple editors which can plug into portlet or access content managed by product like OpenCms, Zope and many others.
The big deal is there, either a lot of jetspeed user need simple editor plugged into portlets or used only jetspeed for content publication. In my case, my customer is not interested to learn Jetspeed + OpenCms or Zope or what ever.
I found in other portal solutions, interesting approach. One of them gives the possibility to edit the content via a 4 simple ways :
* Upload
* Multi line input field. Why not for a very small content
* Ekit which is a java applet editor(hope that there is not license problem for jetspeed)
* Active X HTML editor
We can also provide a jetspeed webdav action. I make some experience with that and seems to be work. When user want to edit a document, he can do that direclty from a rich webdav client and save this content via this webdav action. I propose an action for a better integration with jetspeed.
Compare to Slide, products like OpenCms seems to be more difficult to integrate and it is a nonsense (too many features in common like security management, personnalisation, ...) but maybe accessing their "proprietary" repository is nice (eg. portlet which display a content stored in OpenCms).
If someone has some experience with OpenCms, I'm interesting to know how is it flewible ? Is there a java API ? what about the security model ?
In summary, I think if jetspeed has a CMS repository like Slide + some simple editors + a webdav action, it is a good jump. Later, features like notifications, workflow can be added - What do you think about that ?
Christophe,
No, I'm not a presale guy for Slide :-) It is a simple and good product. One regret : content workflow is missing but it is not really its mains goal.
Weaver, Scott wrote:
AFAIK, Slide is more of api to build a CMS application using WebDAV, not a full featured CMS application like OpenCMS. Someonecorrect me
if I'm wrong.
*===================================* * Scott T Weaver * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] * *===================================*
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
