* 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. Someone correct me if I'm wrong.
*===================================*
* Scott T Weaver *
* Jakarta Jetspeed Portal Project *
* [EMAIL PROTECTED] *
*===================================*
-----Original Message----- From: Mete Kural [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 3:25 AM To: Jetspeed Developers List Subject: RE: CMS service
OpenCMS is LGPL, hence it cannot be distributedWhat about Jakarta Slide, then? Is it as powerful as OpenCMS?
with Jetspeed.
to*===================================* * Scott T Weaver * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] * *===================================*
-----Original Message----- From: Vlachogiannis Evangelos [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 6:29 PM To: 'Jetspeed Developers List' Subject: RE: CMS service
An idea might be to integrate Ekit with OpenCms under JetSpeed so that
Ekit
can save, retrieve, "secure" version and publish files (html,css etc)
http://www.hexidec.com/ekit.phpopencms, which in its turn will publish that content in the form of Jetspeed portlet! In this way jetspeed will be "self-updated" !
-----Original Message----- From: Christophe Lombart [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 1:10 AM To: Jetspeed Developers List Subject: Re: CMS service
In the first time, I propose start with * content upload (Binary or HTML) * HTML editor : simple text field, Ekit and an ActiveX editor Later, an XML Editor : I don't know for explorer - Bitflux seems to be nice for Mozilla There is another one which is more and more popular : Amaya but in this case, it is an external editor. If someone has some experience or mode details to explain on thoses products, I will be very happy.
Vlachogiannis Evangelos wrote:
Hi all,
Here is a free open source Java HTML editor applet and application.
The Ekit standalone also allows for HTML to be loaded and saved, as
well as serialized and saved as an RTF.
[EMAIL PROTECTED]>Vangelis
-----Original Message----- From: Roshan G [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 11:57 PM To: [EMAIL PROTECTED] Subject: RE: CMS service
Here are couple of more opensource Richtext editors to choose from. Unfortunately they only work in IE.
http://www.openmymind.net/products/ewe/index.php (ActiveX based)
http://www.bakedbeanandtomatosoup.co.uk/richtext/default.asp (DHTML)
Roshan
From: "Weaver, Scott" <[EMAIL PROTECTED]>
Reply-To: "Jetspeed Developers List" <jetspeed-
[EMAIL PROTECTED]To: 'Jetspeed Developers List' <[EMAIL PROTECTED]> Subject: RE: CMS service Date: Wed, 18 Jun 2003 09:14:38 -0400
What about another kind of XML editor ? I'm thinking about bitflux (http://bitflux.ch). It is an opensource editor but only working with Mozilla. All other ideas are welcome ! Why not to integrate a small open source HTML editor in the jetspeed demo ?
I know OpenCMS comes with an open source active-x based editor. You may want to start there.
*===================================* * Scott T Weaver * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] * *===================================*
-----Original Message----- From: Christophe Lombart [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2003 6:05 PM To: Jetspeed Developers List Subject: CMS service
Hi All,
One customer of mine gives me more time to work on the CMS service. So, I made some progress in this area (in point of view installation, small demo ,bug fixs, code design, CMS user guide and new features). Are you still interesting to see the code ? Before sending this more advance code, I have to work on how to edit XML content. Do you have some suggestion, preferences in this area ? In my case, we decided to edit the content from Open office or Word (with a nice XML/RTF converter). Certainly, this choice is specific to my customer.
What about another kind of XML editor ? I'm thinking about bitflux (http://bitflux.ch). It is an opensource editor but only working with Mozilla. All other ideas are welcome ! Why not to integrate a small open source HTML editor in the jetspeed demo ?
I know a portal product is dediced to publish content instead of edit content but I think it is certainly interesting for the jetpseed community to have all in one plateform for small cases.
Regards, Christophe
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: jetspeed-dev-
_________________________________________________________________ Tired of 56k? Get a FREE BT Broadband connection http://www.msn.co.uk/specials/btbroadband
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- 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]
