Today I was working on a new feature in the CMS. I had to do some flowscript coding in order to implement this feature. By default you can create an instance of a Java class in flowscript by using the following syntax: cocoon.createObject(Packages.nl.hippo.cms.Class);
I’m sitting outside now in sunny Amsterdam, after catching up some sleep, rethinking the ApacheCon Europe 2006 in Dublin. Arthur, Dennis and myself arrived on wednesday evening, so we had all thursday to attend sessions. Most of them were about AJAX, but there were some other interesting sessions that I really wanted to attend as well.
It looks like some fellow Hippo developers and myself will be attending the ApacheCon Europe 2006 in Dublin next month. This will be my first big Apache Conference with developers from different projects within the Apache Software Foundation. I’m really exited about it and while looking at the sessions, my interest is going out to the Ajax and Apache MyFaces sessions (next to the Cocoon sessions of course).
As you might know, the user experience of a web application is very important. Fast request and response times are a must! You can do so much with Cocoon that sometimes you don’t even know the functionality is there. There is already a lot written about Cocoon performance on the website as well as on the wiki, but over the past couple of years I came across a couple of things that could speed up the performance of you Cocoon web application.
Using XHTML with Cocoon is sometimes a little frustrating. It seems that by using the default XHTML serializer configuration located on the Cocoon Wiki your rendered page is not valid XHTML. While taking a closer look at the configuration (see below) you will notice that it uses the XMLSerializer as its source.