Mixing Iron and Clay: Implementing CMS and Portal as one product

For the last few weeks I've had the joy of working with a portal solution that also provides excellent CMS features. More often than not, portal meets CMS by being a Portal with some junky editor functionality inside, but there are also some CMS'es that feature bits'n'pieces of functionality like portlets, widgets and plugins.

The portal I've been working seems to strike in the middle. It has the richest CMS interface I've come across in a portal product (content structure, versioning, editing all neatly packed into a comfy filthy fat applet client that actually works), and every bit of content is actually an instance of a portlet by its own right (how they've managed to keep the performance so high is quite impressive, and a mystery to me).

This means that not only can I choose each piece of content from a large variety of portlet packages, but I can also transcend content between different states, which is a very handy portlet feature.

However, there is a flip-side to the coin:

Portlets are tiny web-applications. They are powerful, and great once you have them configured. But this means you have to configure them , states and all. You have to compile them, build them, deploy them into the portal, create instances of them and run them before you get to see results.

Additionally, the only content-level storage supported by the portlet spec is portlet preferences, a simple little rag of string data that is used to reference the content of the portlet instance. The spec is a portal-spec, not a CMS spec.

This annoys me as a developer to some degree because I can't utilize the functionality of the underlying content! I can't iterate over the current collection of content. I can't store data in the portlets other than in the portlet preferences, and I can't retreive data other than using the predefined content-portlets that came with the product.

So when I extend the functionality, customizing the CMS if you will, I have to create entire webapps; verticals: database, control layer, web layer and all, in addition to configuring the portlets, states, and then having the deployment hassle of it all.

And at that point I wonder what is the point of having a portal after all....

The answer lies somewhere in the component architecture of the portal. A portal can use many different verticals throughout the application. A webapplication normally uses only one. Oh allright, the webapp can use several as well, but the configuration is all stuck in one place. A portal can combine many different packages of portlets, each having their own web-app configuration, say for instance using their own MVC framework.

This is great, because by the time people get tired of the portlets using Oracle DB with Struts on top, you can replace it with a new DerbyDB/WebWork vertical, exchanging one component that hopefully does not disturb the others. This great is because.. (dramatic pause for today's word of wisdom)...

A framework or technology has a lifespan of max five years. If you throw out and exchange the old components piece by piece, you have a product that will live forever.

I wish there was some third option, getting nice and clean modular webapps without the heavy portal framework. I know there is a solution out there, we just need somebody to sit down and figure it out, then share the knowledge with the rest of us.

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...