Skip to main content


Showing posts from September, 2006

The Evolution of Content Management

Edit: Seems Writely doesn't publish images onto here. Argh.

It is challenging to make a clear distinction that separates WCM systems from similar information systems. To explore this one must understand the possible ways to do web content management. Various architectures of implementation exist. One possible categorization is presented here. These four levels are a way to divide the physical management of content. In general one can say that the higher use of web content in a company, the higher level its WCMS implementation should be. The separation is historical and drawn from my personal experience with web development through the last decade, therefore the evolutionary approach.Static files on a web-serverThe most basic strategy is to compose static HTML files and transfer these to a web server capable of serving such files to clients connecting to the web-site. It is possible to apply styles to the pages, for example with the help of cascading style-sheets (CSS).Content wrapp…

JavaZone report, rest of day 1 and day 2

Updated with hyperlinks
Day 1Well, I didn't go to Bjørn's presentation anyway for some reason. Some chaos at the stand, and I dropped into the presentation on Matisse. Long story short, this stuff is Visual Studio five years ago, the live demo botched terribly, and I did a walk-out after about 20 minutes. Geertjan explained why in his blog, and it looked like a dependancy management problem. Snap out of it, guys. Ditch Ant and start using Maven. Still, looking at the state of Swing, I'm glad I'm doing web-apps.

Then I took some time off to handle stand-chaos, and eat with Erling (old student buddy) who I haven't met in a while. I was also in the Meet-The-Gurus: MVC framework smackdown with Arjen Poutsma (Interface 21/Spring MVC), Rickard Öberg (creator of WW) and Kaare Nilsen (JSF). Was interesting to see how the MVC frameworks (or web frameworks as I prefer to call them) could be divided into several channels of motivation, and thus is the reason we have so many fr…

JavaZone report, day 1, half-done

Updated with hyperlinks

Was at Bruce Johnson's talk on Google WTK. Cool stuff, Google, nuff said. Will have to try it out.

Then on to Jevgeni Kabanov's talk on Arenea. Interesting ideas, but I don't really think this is anything ready for prod. I'm an OO guy, so I can really see the use of using more OO in webapps. Might try this out next year if it's still alive.

Took a one session break.

Now in Bruce Tate's Java/Ruby integration talk. So far doing very well being diplomatic towards java (perhaps very wisely). Alotta RoR demonstration, and the ReST stuff was of course impressive. Tate is by the way one helluva talker. Sounds a bit like an American president (scaringly smoothly convincing type), but I think he's Texan, after all :)

Now I've stumbled into Ross Mason's Mule/JavaSpaces . The nickle in his shoe is handling meta-data for web services. but ESBs, or was it WSDLs, don't provide this too well.

Now normally I like to stay clear of the serv…

See you at JavaZone!

Righto, wednesday is the big day! JavaZone really looks to be one of the coolest Java conferences ever, and it's right here in Oslo! Quite amazing. Will try to blog a bit about the presentations I get to see, but will also be hanging around Objectware's stand alot, eating popcorn (come get some, it's free!).

Replacing a repository

They say you should blog about something you like, stick to the subject, be informal, and write something useful. Add subjective knowledge to the community.

My thoughts on the field of content management haven't really evolved much since I began working one month ago, but I have encountered a portal/CMS system which I sooner or later will have to use and develop with, I guess. Now the sorry thing about this portal is that I can't utilize my experience with the Java content repository (JCR) standard JSR-170. The portal vendor *could* implement support for it, but as I guess the internal datastructure is, this would lead to an entire replacement of the existing repository, throwing some years of development and use out of the window.

My gut feeling tells me this would not be worth it at this point. But for the sake of argument, let's wheigh the implications of replacing a homegrown repository with for instance Jackrabbit.

Negative implicationsImplementation. The datastructur…