Existing WCMS-es

This is a from an internal discussion at work..

Jahia seems nice on the demo, but they are quite outdated on the open source part (using old stuff like struts and ant, no JSR-170). Same thing goes for the very popular Liferay.

Swedish SiteVision is also good, but Objectware have alread got the under their hood. Magnolia as well, but the (like us) are based on persisting the content with Jackrabbit, and at this point there is no DBMS support there (though this is right around the corner). Magnolia's developers, the commercial company Obinary, are offering their customers an other JSR-170 compliant repository: CRX from Day. I suspect that the CRX is heavily based on Jackrabbit, since the Day developers are the core of the Jackrabbit crew.

Here's an incomplete overview:

Company      Open Source produt         Commercial product
-------------------------------------------------------------
Obinary      Magnolia                   Compass
Day          Jackrabbit                 CRX
Senselogic   --                         SiteVision
eXo          eXo Platform               --
Liferay      Liferay                    --
Alkacon      OpenCMS                    --
Us           --                         P

All the companies above also gather some revenue in consulting and hosting services.

So where should we position ourselves? We could keep developing our own CMS and
use Jackrabbit at persistence level, but that would leave us in competition with
Obinary (which is not where we want to be).

Perhaps we should build on Magnolia instead of making something on our own.
It would save us quite an amount of development with the cost of giving us
a lesser understanding and custom-tailoring of the CMS. But we feel we will
make up for the lack of functionality by spending the time saved on making
Magnolia extensions and modules.

This could lash right back our face. Magnolia can turn out to be too complicated
for someone outside Obinary to understand (like our previous CMS stroke us) and
too hard to modify for our customers' needs.

We also have to consider the transaction of articles and data from the old
database onto the JCR. We might even (like Magnolia) have to invest in an more
solid JCR implementation like CRX to ensure scalability, if Jackrabbit proves
incomplete to the task, that is.

Day has a nice faq about CRX and JCR:

http://www.day.com/content/en/product/jsr_170/content_repository/crx_faq.html

CMS-wizeguy Öbergs ramblings:
http://www.theserverside.com/news/thread.tss?thread_id=32890#164178

The more I think about it, and study our competitors, the more convinced I
become that we should build on what others have built. I'm worried that if
we keep developing a CMS on our own, it will take too much resources, and
no matter what always reside some paces behind Magnolia.

We've spent some time increasing our knowledge of Jackrabbit, JSF, Tomcat
and other useful technologies. Perhaps this knowledge is better put to work
if we join up with the present kings of content (kongene på haugen).

Comments

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password...

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git -> ~/.atom/* config-mr.git -> ~/.mrconfig -> ~/.config/mr/* config-tmuxinator.git -> ~/.tmuxinator/* config-vim.git -> ~/.vimrc -> ~/.vim/* config-bin.git -> ~/bin/* config-git.git -> ~/.gitconfig config-tmux.git -> ~/.tmux.conf config...