[opencms-dev] convert Vignette sites to OpenCMS

[Bernard, Shawn]

Those are excellent points.  As far as Vignette functionality, we are using Tcl and caching.  We are NOT using records or workflow (because Vignette workflow sucks - we'd like our next CMS solution to include a usable workflow component).  We understand that there will definately be a lot of work porting from Tcl to JSP/Java, and we are willing to take that hit.

We are dedicated to using JSP/Java in our next CMS, too.  We have a number of excellent JSP/Java people in our department and we want to leverage that knowledgebase.  Going to something like PHP (as much as I like it) does not seem like an option.
 
What Vignette is to us, basically, is all backend stuff.  We are not using their personalization, or other components.  We are using it, basically, as a development environment.  When we switch over, we need to be able to keep the functionality, from a user's perspective, the same.  The datamodel/DB cannot change (except, perhaps, very minor changes).

I've been poking around at OpenCMS and Red Hat CCM (formally ArsDigita).  They both feel a little confining for my tastes, but maybe that's because I do not have very much experience with either of them.  It seems that, at this point, just using JSP/Java (Tomcat, etc.) and using CVS for version control, and perhaps oscache for the caching mechanism, seems like a strong possibility.  Of course, we'll have to sacrifice workflow and other things like that, but maybe that's a bullet that we have to bite.

Shawn

-----Original Message-----
From: Matthias Nott [mailto:matthias.nott at businessobjects.com]
Sent: Thursday, January 09, 2003 3:30 PM
To: opencms-dev at www.opencms.org
Subject: AW: [opencms-dev] convert Vignette sites to OpenCMS


Shawn,
 
The basic question will be whether or not they are actually using the Vignette functionality. I know Vignette
up to V/6 pretty well and see the following bits that may be of interest:
 
a) caching (could be replaced e.g. by opensymphony.org/oscache)
b) url rewrite (can be replaced by e.g. mod_rewrite)
c) "records" (you perhaps don't want to use them in the first place)
d) which language do they use - vign supports JSP (ok, say, they have a Java API), but many sites are still Tcl
 
So basically there is no general answer to your question, except that _yes_, there are many open source cms'es
around that can deliver many things very similar, or even superior to at least what I know (pre-V/7). Some
of the hottest candidates are opencms (Java), and, in terms of functionality probably even more advanced, Typo3
(PHP).
 
A very simple question you can seriously ask your customers is this: What are you actually using from
your CMS functionality?
 
Cheers,
 
M
 

-----Ursprüngliche Nachricht-----
Von: owner-opencms-dev at www.opencms.org [mailto:owner-opencms-dev at www.opencms.org] Im Auftrag von Bernard, Shawn
Gesendet: Thursday, January 09, 2003 8:12 PM
An: 'opencms-dev at opencms.com'
Betreff: [opencms-dev] convert Vignette sites to OpenCMS



We have a bunch of sites running on Vignette, and all of them have a very complex, unique content management system.  Each has its own unique datamodel and content management application, as well as content display application.

We are considering moving away from Vignette and to an open source CMS that supports JSP/Java. 

Does anyone have any experience porting over complex sites to OpenCMS?  It is absolutely necessary that we keep the current datamodels of the sites, as well as all the functionality of the sites' content management applications.

Does anyone out there have experience with this?  Is this even possible?  Or will I have to adopt the OpenCMS methodology/model of doing content management?

Thanks, 

Shawn 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20030109/155df0d1/attachment.htm>