hi Scott, Thanks for your response. It helped me to understand some issues.
Sorry that I just read about the CMSService idea some minutes after my post. What i think is, Jetspeed should work with any CMS, but not that Jetspeed include a CMS by itself. I think the CMSService idea does achieve this. I misunderstood that we want to add CMS features to Jetspeed, which is not too good. Integration is a perfect idea. However, I still hold the thought that Jetspeed's integration with Turbine is not too good for CMS integration. > You will need to qualify exactly what in Turbine/Jetspeed was > crashing your CMS. That's not really what I want to raise. If I need to qualify with example, I will give the example of OpenCMS. I tried to use Struts (just consider it is nothing but a controller servlet) with OpenCMS, but without success. (i would need some time to recall the details from memory, let me know if you're interested.) There may be some solutions as I didn't have time to try everything out. Take an example, the Turbine provides a template system, and most cms provide one as well. I presume I should use the CMS one cause I can't enjoy content management service without using it. Re. portlet api, my idea is, we simply use the portlets in the CMS, (that include the portlets, customerization etc) and forget all the other features of Jetspeed (e.g. security/user/authentication, template, caching etc, basically, all turbine things, which is provided by CMS). This idea obviously apart from the Jetspeeders way of thinking! (well, I suggest to give up the work that was done. please feel free to criterize the idea!) :-) regards, mingfai p.s. I just read about documentum's "Content Service for Portals". I am curious on how does it work and I wonder it's similar to the CMSService as mentioned. http://www.documentum.com/products/glossary/cs_for_portals.htm > -----Original Message----- > From: Weaver, Scott [mailto:Sweaver@;rippe.com] > Sent: Thursday, October 24, 2002 1:24 AM > To: 'Jetspeed Users List' > Subject: RE: CMS > > > > btw, why this thread isn't in the Jetspeed developer list? > there should be > > more Jetspeed experts there to comment. > > The initial thread I started about week ago did move to dev, > however, the discussion dropped off. > > > Another issue is, Jetspeed is supposed to be a portal server. I > personally > > think it shouldn't be a CMS itself and it should be made to integrated > > with > > any CMS in the market. How do you think? > > The CMS would be an underlying service that would theoretically > be able to plug into anything that required CMS. From Jetspeed, > one would create portlets to interact with this service. > > > I got the thought of integrating Jetspeed with CMS, but I think, the > > current > > Jetspeed is too cohere with Turbine, which crashes with many > CMS features. > > You will need to qualify exactly what in Turbine/Jetspeed was > crashing your CMS. > > > It seems to me a pure Portlet API (I suppose the JSR 168 is going to > > define > > one and Jetspeed will become/include an reference implementation of it) > > will > > integrate with CMS in a much better way. > > IMOHO, the portlet implementation has nothing to do with writing > a CMS system or integrating with it. As a stated above you need > to have a good separation of concerns where the CMS runs as a > service itself that is jump started by Jetspeed on startup. > Basically you would have a Fulcrum service accessed by a set of > pull tools and portlets. The CMS would not be a portlet unto > itself and could be easily separated from Jetspeed. All that > jetspeed would is offer a view/interaction layer that talks to > the CMS implementation and possibly supplies security which > should be pluggable also. > > > > Scott > > > -----Original Message----- > > From: Ming Fai [mailto:mingfai@;hongkong.com] > > Sent: Wednesday, October 23, 2002 12:41 PM > > To: Jetspeed Users List > > Subject: RE: CMS > > > > hi, > > > > Two other good (the two best, in my opinion) Open Source Java CMS are > > Redhat > > CCM (http://ccm.redhat.com/) and OpenCMS (www.opencms.org). > > > > I got the thought of integrating Jetspeed with CMS, but I think, the > > current > > Jetspeed is too cohere with Turbine, which crashes with many > CMS features. > > It seems to me a pure Portlet API (I suppose the JSR 168 is going to > > define > > one and Jetspeed will become/include an reference implementation of it) > > will > > integrate with CMS in a much better way. > > > > For the same reason as above, it will not be a nice job to integrate > > Jetspeed (with Turbine) with a Struts-based application. I > analysed Struts > > and Turbine a year ago and they are overlapping in function. > > > > Regarding slide, I know a bit about it. To my understanding, it mainly > > provides a WebDAV engine that help to develop content update > function of a > > CMS. (Please correct me if I'm wrong) It has a long way to go to have a > > usable CMS integrated Jetspeed. Slide may help in developing a content > > update form, but a huge effort will be needed to, say, build a online > > WYSIWYG editor. A typical CMS provides features like a > templating system, > > content catagorization, content indexing and search, workflow, > scheduling > > etc. I wonder how much Slide can do in the above areas. > > > > Another issue is, Jetspeed is supposed to be a portal server. I > personally > > think it shouldn't be a CMS itself and it should be made to integrated > > with > > any CMS in the market. How do you think? > > > > btw, why this thread isn't in the Jetspeed developer list? > there should be > > more Jetspeed experts there to comment. > > > > regards, > > mingfai > > > > > -----Original Message----- > > > From: Weaver, Scott [mailto:Sweaver@;rippe.com] > > > Sent: Thursday, October 24, 2002 12:21 AM > > > To: 'Jetspeed Users List' > > > Subject: RE: CMS > > > > > > > > > Stuart, > > > > > > David sent me Tom Keeney's stuff already. There is an issue with > > > the licensing, as it is non-distributable and David was unable to > > > contact Tom Keeney via email. > > > > > > I have compared Christophe's and Tom's work an I think I prefer > > > Christophe's because it has Slide directly using Jetspeed's > > > security without having to create a custom Jetspeed user and > > > without creating duplicate profiles for users in both Slide and > > > Jetspeed. Christophe has done a nice job in creating custom > > > Slide stores that directly access Jetspeed security. > > > > > > Scott > > > > > > > -----Original Message----- > > > > From: Stuart Belden [mailto:SBelden@;bjc.org] > > > > Sent: Wednesday, October 23, 2002 11:59 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: RE: CMS > > > > > > > > I'm also working on a CMS to use in Jetspeed. I started writing my > > own > > > > as Slide unfortunately didn't meet my requirements. I know this was > > > > re-posted not that long ago, but Tom Keeney did work with Slide and > > > > Jetspeed user integration that he sent back in August. I've had a > > > > couple requests for the files that went along with his email, which > > I've > > > > posted at: http://www.stumod.com/jetspeed.html. I'll happily take > > them > > > > down if there's an issue with me hosting them. > > > > > > > > I may have some time to contribute to a Jetspeed CMS project in some > > > > way or the other. I also second the idea of content management over > > > > creation and creating a plugable service. > > > > > > > > > > > > >>> [EMAIL PROTECTED] 10/23/02 10:15AM >>> > > > > That sounds great Jose! The more ideas we can get the better. I > > > > would still like to focus on using Slide. However, it would be very > > > > cool to be able to plug in different content management api's to > > support > > > > the CMS capabilities within jetspeed. We could create a generic > > > > CMSService and then write different implementations for it starting > > with > > > > a SlideCMSService as the default. > > > > > > > > Scott > > > > > > > > -- > > > > To unsubscribe, e-mail: <mailto:jetspeed-user- > > > > [EMAIL PROTECTED]> > > > > For additional commands, e-mail: <mailto:jetspeed-user- > > > > [EMAIL PROTECTED]> > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:jetspeed-user- > > [EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:jetspeed-user- > > [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
