<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:posterous="http://posterous.com/help/rss/1.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
  <channel>
    <title>Serge's content</title>
    <link>http://sergehuber.jahia.com</link>
    <description>Thoughts on WCM and related technologies</description>
    <generator>posterous.com</generator>
    <link xmlns="http://www.w3.org/2005/Atom" href="http://posterous.com/api/sup_update#237635813" type="application/json" rel="http://api.friendfeed.com/2008/03#sup" />
    
    
    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/jahia/serge" /><feedburner:info uri="jahia/serge" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://posterous.superfeedr.com/" /><item>
      <pubDate>Mon, 07 Nov 2011 01:28:00 -0800</pubDate>
      <title>Quick Mac Tip : install Java 1.5 on OS X Lion</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/6jO7m9fDvEg/quick-mac-tip-install-java-15-on-os-x-lion</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/quick-mac-tip-install-java-15-on-os-x-lion</guid>
      <description>&lt;p&gt;
	&lt;p&gt;If you're like me, you might need to test compatibility with Java 1.5 despite the fact that it's old and that nobody should use it anymore :) Unfortunately the reality is that some users migrate slowly, and so it might be useful to be able to test with old versions of the JDK.&lt;/p&gt;
&lt;p&gt;As you probably know, the JDK 1.5 is not available officially for Mac OS X Lion. But there is a way to install it anyway, and it is very well documented here :&amp;nbsp;&lt;a href="http://www.s-seven.net/java_15_lion" title="Install Java 1.5 on Mac OS X Lion" target="_blank"&gt;http://www.s-seven.net/java_15_lion&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Let me know if you liked this tip, I might add more in the future :)&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/quick-mac-tip-install-java-15-on-os-x-lion"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/quick-mac-tip-install-java-15-on-os-x-lion#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=6jO7m9fDvEg:2Dhklp8C2T8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=6jO7m9fDvEg:2Dhklp8C2T8:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=6jO7m9fDvEg:2Dhklp8C2T8:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=6jO7m9fDvEg:2Dhklp8C2T8:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/6jO7m9fDvEg" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/quick-mac-tip-install-java-15-on-os-x-lion</feedburner:origLink></item>
    <item>
      <pubDate>Fri, 04 Nov 2011 01:41:04 -0700</pubDate>
      <title>Some fun with videos</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/zXa90uBDg9k/some-fun-with-videos</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/some-fun-with-videos</guid>
      <description>&lt;p&gt;
	I had some fun with the iMovie trailers functionality the other day and did this quick ad for Jahia 6.5 which I think turned out quite well. What do you think about it ?&lt;p /&gt;&lt;div&gt;&lt;iframe src="http://player.vimeo.com/video/30380316?portrait=0" frameborder="0" height="283" width="500"&gt;&lt;/iframe&gt;&lt;/div&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/some-fun-with-videos"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/some-fun-with-videos#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=zXa90uBDg9k:G_3LldzOaOs:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=zXa90uBDg9k:G_3LldzOaOs:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=zXa90uBDg9k:G_3LldzOaOs:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=zXa90uBDg9k:G_3LldzOaOs:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/zXa90uBDg9k" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/some-fun-with-videos</feedburner:origLink></item>
    <item>
      <pubDate>Fri, 04 Nov 2011 00:15:00 -0700</pubDate>
      <title>A few new things...</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/xFNE1Cn1OTI/a-few-new-things</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/a-few-new-things</guid>
      <description>&lt;p&gt;
	&lt;p&gt;For those of you that have been following my blog (btw thanks !), and for the newcomers, I'd like to announce a few new things coming to this blog. First and foremost, there should be more activity here, as I have been able to shift around some of my time towards more outside communication now that we have version 6.5 out the door.&lt;/p&gt;
&lt;p&gt;What this means is that you will get a new kind of posts in this blog : samples. I will use these samples to illustrate what can be achieved using Jahia as a basis for integration of all kinds of technologies such personalization, real-time server statistics, and much more !&lt;/p&gt;
&lt;p&gt;Of course I won't forget to have some fun, and post some videos that we have made to promote or illustrate some of the lighter sides of our work.&lt;/p&gt;
&lt;p&gt;I must say I am very excited about the new Jahia 6.5 release, and I can't wait for you to try it ! You can download it here:&amp;nbsp;&lt;a href="http://www.jahia.com/cms/home/download.html" title="Jahia Download Page" target="_blank"&gt;http://www.jahia.com/cms/home/download.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/a-few-new-things"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/a-few-new-things#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=xFNE1Cn1OTI:KVBg1N0oJkc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=xFNE1Cn1OTI:KVBg1N0oJkc:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=xFNE1Cn1OTI:KVBg1N0oJkc:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=xFNE1Cn1OTI:KVBg1N0oJkc:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/xFNE1Cn1OTI" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/a-few-new-things</feedburner:origLink></item>
    <item>
      <pubDate>Fri, 16 Sep 2011 03:09:00 -0700</pubDate>
      <title>OSGi in 5 minutes</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/yqEjlr1dfkQ/osgi-in-5-minutes</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/osgi-in-5-minutes</guid>
      <description>&lt;p&gt;
	&lt;p&gt;I just put together quickly this presentation that aims to be a very quick introduction to OSGi. I look forward to any feedback :)&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div style=""&gt;&lt;strong style="display: block; margin: 12px 0 4px;"&gt;&lt;a href="http://www.slideshare.net/sergehuber/osgi-in-5-minutes" title="OSGi in 5 minutes" target="_blank"&gt;OSGi in 5 minutes&lt;/a&gt;&lt;/strong&gt; &lt;iframe scrolling="no" marginheight="0" marginwidth="0" src="http://www.slideshare.net/slideshow/embed_code/9280626" frameborder="0" height="355" width="425"&gt;&lt;/iframe&gt;
&lt;div style="padding: 5px 0 12px;"&gt;View more &lt;a href="http://www.slideshare.net/" target="_blank"&gt;presentations&lt;/a&gt; from &lt;a href="http://www.slideshare.net/sergehuber" target="_blank"&gt;Serge Huber&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/osgi-in-5-minutes"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/osgi-in-5-minutes#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=yqEjlr1dfkQ:bo_L2aMmgOM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=yqEjlr1dfkQ:bo_L2aMmgOM:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=yqEjlr1dfkQ:bo_L2aMmgOM:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=yqEjlr1dfkQ:bo_L2aMmgOM:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/yqEjlr1dfkQ" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/osgi-in-5-minutes</feedburner:origLink></item>
    <item>
      <pubDate>Mon, 17 Jan 2011 22:47:00 -0800</pubDate>
      <title>Integrate Maven and Growl</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/vV1HLrQIJE8/integrate-maven-and-growl</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/integrate-maven-and-growl</guid>
      <description>&lt;p&gt;
	&lt;p&gt;Don't you have the problem that you launch Maven builds that take some time to execute and in the meantime you switch to something else ? The problem is that often the build finishes in the background and it's only later that you come back to it, once you've finished your foreground task.&lt;/p&gt;
&lt;p&gt;Well I do that a lot, and I found this &lt;a href="http://geoffreywiseman.github.com/maven-growl/" title="Integrate Maven and Growl" target="_blank"&gt;great little tutorial on how to integrate Maven and Growl&lt;/a&gt; on the Mac. There are probably ways to do this also on Windows and Linux I'm quite sure, but as the Mac is my main development platform, I will leave others to take care of the other platforms :)&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Install growlnotify from the Extras package in &lt;a href="http://growl.info/" title="Growl's Web site" target="_blank"&gt;Growl's standard package&lt;/a&gt; :&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Add a script in your MAVEN_HOME/bin directory called "gmvn" with the content :&amp;nbsp;&lt;code&gt;&lt;br /&gt;#!/bin/bash&lt;br /&gt;mvn $*&lt;br /&gt;if [ $? -gt 0 ]&lt;br /&gt;then&lt;br /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;echo "Build failed!" | growlnotify "Maven" --name maven --image ABSOLUTE_PATH_TO_IMAGES/maven-growl-failure.jpg &amp;gt; /dev/null 2&amp;gt;&amp;amp;1&lt;br /&gt;else&lt;br /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;echo "Build completed successfully." | growlnotify "Maven" --name maven --image&amp;nbsp;ABSOLUTE_PATH_TO_IMAGES/maven-growl-success.jpg &amp;gt; /dev/null 2&amp;gt;&amp;amp;1&lt;br /&gt;fi&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;chmod +x gmvn&lt;/li&gt;
&lt;li&gt;Then use gmvn instead of mvn to build your projects.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;You can retrieve the images from &lt;a href="http://geoffreywiseman.github.com/maven-growl/" title="Geoffrey's web site" target="_blank"&gt;Geoffrey's website&lt;/a&gt;. Note that you will have to specify an absolute path to the images. For some reason a relative path doesn't seem to work.&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/integrate-maven-and-growl"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/integrate-maven-and-growl#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=vV1HLrQIJE8:QPOC_RConVA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=vV1HLrQIJE8:QPOC_RConVA:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=vV1HLrQIJE8:QPOC_RConVA:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=vV1HLrQIJE8:QPOC_RConVA:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/vV1HLrQIJE8" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/integrate-maven-and-growl</feedburner:origLink></item>
    <item>
      <pubDate>Mon, 17 Jan 2011 07:20:00 -0800</pubDate>
      <title>JCR is not dead, and neither is CMIS</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/2seWQHiCfy8/jcr-is-not-dead-and-neither-is-cmis</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/jcr-is-not-dead-and-neither-is-cmis</guid>
      <description>&lt;p&gt;
	&lt;p&gt;Recently, an &lt;a href="http://www.cmswire.com/cms/web-cms/is-jcr-dead-009676.php" title="CMS Wire &amp;quot;Is the JCR dead&amp;quot; article" target="_blank"&gt;article on CMSWire&lt;/a&gt; caused quite a stir, mostly because it was asking the controversial question "Is the JCR dead ?". In reply, a few opinions posted by myself and other CMS actors/vendors were quick to appear, but I think some clarification is needed in order to explain what I think is really relevant for developers, integrators and end-users.&lt;/p&gt;
&lt;p&gt;The quick answer is : neither &lt;a href="http://jcp.org/en/jsr/detail?id=283" title="JCR 2.0 Specification" target="_blank"&gt;JCR&lt;/a&gt; nor &lt;a href="http://www.oasis-open.org/committees/cmis/" title="CMIS Working Group" target="_blank"&gt;CMIS&lt;/a&gt; are really important for end-users. Fortunately most of them will never have to deal with either, and only integrators and developers will have to bother.&lt;/p&gt;
&lt;p&gt;Now these two standards were put in opposition in the article, probably in the hope that the controversy would attract readers, but it actually doesn't make sense to do that. A lot of developers are actually using both, and the only real difficulty in integrating the two is translating queries, but apart from that it maps pretty well.&lt;/p&gt;
&lt;p&gt;The JCR is not dead and still relevant, because other standards such as &lt;a href="http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136101.html" title="JDBC" target="_blank"&gt;JDBC&lt;/a&gt; are not dead and also still relevant. A lot of people wanting to see the JCR die have probably had bad experiences with it, or have moved on to other technologies, but this standard still make a lot of sense in the Java CMS and &lt;a href="http://en.wikipedia.org/wiki/Web_content_management_system" title="Web Content Management" target="_blank"&gt;WCM&lt;/a&gt; world. Where else can you get a native language API that offers powerful queries, versioning, flexible content definitions, import/export etc ? Sure CMIS offers some of these, but at the same time you probably wouldn't want to use CMIS in the middle of your Java project. CMIS is mostly oriented towards being a service interface.&lt;/p&gt;
&lt;p&gt;One may want to ask the question : if my technology exposes as a service, why even bother with a middleware standard such as JCR ? Mostly because JCR addresses some standard features that are hard to implement well, such as advanced queries or versioning, and standardizing the interface allows for a reliable layer at which to write tests and implement things properly. For example, query parsing and execution can be complex, and having a standard to define it them good both for interoperability, migration and overall quality. This doesn't mean that it doesn't have any drawbacks, as is the case for example in the amount of query languages supported, which really should be reduced in the next version, because it complexifies the implementations. In JCR 2.0 it is possible to query for content using the SQL-2 language or the Abstract Query Model, but also with the SQL-1 or XPath languages that were part of the 1.0 specification and are now deprecated. What this implies is that the default implementation, &lt;a href="http://jackrabbit.apache.org/" title="Apache Jackrabbit" target="_blank"&gt;Jackrabbit&lt;/a&gt;, has to support all four of these query systems at this point, and this makes the implementers' job all that more difficult, and optimizations are equally hard to do. This problem is a transitional one, and one can hope it will be resolved in the next version, as the old languages are already deprecated.&lt;/p&gt;
&lt;p&gt;Another important and difficult to implement sub-system is versioning. We, at Jahia, have noticed how complex this can become when doing advanced versioning operations on trees. A good example is &lt;a href="http://www.nongnu.org/cvs/" title="CVS" target="_blank"&gt;CVS&lt;/a&gt;, which couldn't support moves, because of the complexity that is needed to properly version such operations. It is only much later, and with a different model, that &lt;a href="http://subversion.tigris.org/" title="Subversion" target="_blank"&gt;SVN&lt;/a&gt; managed to fill the gap. All this to say that standardization of these features allows to make sure that they are well defined, and that JCR users can rely on such features to build value on top of it. It also means that in the case of open source implementations of the JCR, people may collaborate to develop and maintain such complex code. The alternative is to redevelop this all from scratch in a non-standard way, and coming from this world I can tell you it is not the best option for neither the developers, integrators nor the end-users.&lt;/p&gt;
&lt;p&gt;The above are just two examples of why this standard actually help build common infrastructure, and make sure that backend features are available. There are many more features that are part of the standard, such as ACLs, content definitions, import/export, observation, workspaces, transactions that are equally part of the infrastructure that most developers want to take for granted, rather than re-implement.&lt;/p&gt;
&lt;p&gt;As I have mentioned previously, my biggest gripes with CMIS is that it is too file-oriented, and that it lacks a simple interface. Maybe I should explain what I mean by simple interface. Today, in the world of &lt;a href="http://rubyonrails.org/" title="Ruby on Rails" target="_blank"&gt;Ruby on Rails&lt;/a&gt;, &lt;a href="http://sling.apache.org/" title="Apache Sling" target="_blank"&gt;Apache Sling&lt;/a&gt;, &lt;a href="beta65.jahia.org" title="Jahia 6.5 Beta" target="_blank"&gt;Jahia 6.5&lt;/a&gt;, &lt;a href="http://www.day.com/" title="Day's Communique" target="_blank"&gt;Day's Communique&lt;/a&gt;, people want simple (yet still powerful) access to their content objects. All the aforementioned tools allow for simple &lt;a href="http://en.wikipedia.org/wiki/Representational_State_Transfer" title="REST" target="_blank"&gt;REST&lt;/a&gt; HTTP mapping of URIs and attributes to back-end content objects. CMIS 1.0 still requires that you use either ATOM or SOAP to interact with content objects, and even so a lot of wiring is still required. Of course one of the goals of CMIS is that tools and libraries will be available to help with the integration, but it will be hard to beat the simplicity of a simple HTTP POST request to update content.&lt;/p&gt;
&lt;p&gt;I have been following the CMIS open-source implementation at Apache, and the efforts are really great, but it hit a major roadblock when it switched implementation in the middle of last year, moving from the old Chemistry codebase contributed by Nuxeo to the one contributed by OpenText. It took a little while to merge all the functionality, and it has now reached a point where it is really interesting, at version 0.2.0. Of course at Jahia we are integrating with &lt;a href="http://incubator.apache.org/chemistry/" title="Apache Chemistry" target="_blank"&gt;Apache Chemistry&lt;/a&gt;, but as we had worked with the old code base, we had to restart when the implementation changed. This is probably true of other people working with CMIS. So in no way do I want to diminish the importance of CMIS, but between the wild claims that are out there that CMIS will revolutionize the world and the hard truth of the code available in open source or closed source implementations, there is still a lot of work.&lt;/p&gt;
&lt;p&gt;I hope there will be an emerging service standard that will fulfill the promise of being both flexible and easy to integrate, and this ends up to be CMIS so much the better. But let's not forget that before CMIS there was iECM, WebDAV, and before that many more that didn't work because of the complexity of the implementations, or because vendors never really committed to interoperability. It is also hard to keep a standard minimal, and at version 1.0 CMIS is already much more complex than I had hoped it would be.&lt;/p&gt;
&lt;p&gt;I have also said that one of the main reasons people are interested in CMIS is that the standard is that Microsoft is onboard with the inclusion of an implementation in Sharepoint 2010. But let's not forget that Microsoft has a pretty bad history of keeping up with standards. One often forgotten example is WebDAV, called Web Folders in Windows. Initially a lot of people were very happy to see Microsoft implement this at the OS level, but very quickly, as the standard evolved, the WebDAV implementation that Microsoft built was not property maintained and therefore not seen as very important for them as a interoperability strategy, especially compared to .NET and SOAP. As times passed, Microsoft started replacing WebDAV with SOAP interfaces, and this is reflected in the current state of the integration between MS Office and Sharepoint.&lt;/p&gt;
&lt;p&gt;On the Java side, I believe there is no current standard alternative to the JCR, and the alternative of having vendor lock-in on the lower levels is actually a little scary. We've had a custom built content repository for years before we integrated with the JCR, and maintaining this within our company was not the best way to focus our resources on something that should be common infrastructure, much in the same way we would never think of re-implementing our own database.&lt;/p&gt;
&lt;p&gt;When working on a WCM, you really need to be able to handle tree-like structure, with varying properties depending on the position in the tree, with advanced features such as versioning, permissions, locking, structure definitions, in an API that is native to the language in which you are writing your WCM product. This is what the JCR is for and what it is good at. It is NOT a service API. It would be equally crazy to use CMIS within an implementation of a WCM, because this means that each access to a content object would have to go through layers of transformations to handle the ATOM or SOAP calls. But if you are working on integrating loosly coupled data repositories, with a lower volume of calls, then using CMIS makes a lot more sense. This is why CMIS works well with files, but not as well for generic content objects.&lt;/p&gt;
&lt;p&gt;So in conclusion, I think that a lot of noise was generated around all this, but the good news is that standards do exist and they are alive and well, and let's hope that their evolution will make them even better. But the real interesting work is above all this, to make content easier to generate, curate, share and retrieve.&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/jcr-is-not-dead-and-neither-is-cmis"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/jcr-is-not-dead-and-neither-is-cmis#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=2seWQHiCfy8:-5PKpJ2k0IQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=2seWQHiCfy8:-5PKpJ2k0IQ:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=2seWQHiCfy8:-5PKpJ2k0IQ:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=2seWQHiCfy8:-5PKpJ2k0IQ:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/2seWQHiCfy8" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/jcr-is-not-dead-and-neither-is-cmis</feedburner:origLink></item>
    <item>
      <pubDate>Fri, 06 Aug 2010 03:11:00 -0700</pubDate>
      <title>Open source makes your customers happier</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/X8UFBcRiUIg/open-source-makes-your-customers-happier</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/open-source-makes-your-customers-happier</guid>
      <description>&lt;p&gt;
	&lt;p&gt;I often get the question of why open source code is important, aside from the usual benefits of code review, security auditing, and the general idea that more eyeballs makes for better implementations ?&lt;/p&gt;
&lt;p&gt;Well, where it really shines is during support, when you are investigating a bug.&lt;/p&gt;
&lt;p&gt;Let's say that you have a bug, and that for once it is not in your code. It seems to come from some library that is used by your software. When this happens, for example when I'm working on an &lt;a href="http://www.apple.com/iphone"&gt;iPhone&lt;/a&gt; application, it usually takes a long time to find the method responsible for the bug. If the libraries are closed-source, this time can be made longer simply by the fact that you are not sure what the dependencies between libraries are, and can spent time trying to pin-point the location of the problem. Once you have managed to track it, all you can do is file a bug report to the author, and hope it will be adressed. In this example case of an iPhone application, this might be a long time, if ever it gets fixed (as bugs are proritized by project managers).&lt;/p&gt;
&lt;p&gt;In the case of an open source product, such as &lt;a href="http://www.jahia.com"&gt;Jahia&lt;/a&gt;, you have the full source code, and you are free to modify it for your own means, or redistribute the modification under the same license. So this means that when tracking down a bug, I can not only more rapidly find the origin of the problem, but I can, if I know how to do it, correct it myself and not have to rely on external resources that may not be available at the time. Also, when debugging, it is really great to be able to trace through the code to understand what is going on. Maybe the bug is in your own code, but actually seeing the source code of the external library made you understand what was wrong in your own code a lot faster. You could ask an external consultant to work on it, and he could do it provided he has a good knowledge of the code, and help you fix the issue faster. Finally you can contribute the fix back to the author of the source code if the issue was found in an external piece of software.&lt;/p&gt;
&lt;p&gt;So in the end, bugs get identified and fixed faster, you spend less time with bugs, the customer gets a answer faster, basically everyone wins.&lt;/p&gt;
&lt;p&gt;This is for me one of the biggest commercial advantages of open source against closed source, and if it makes the customer happier, it means you will retain him.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/open-source-makes-your-customers-happier"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/open-source-makes-your-customers-happier#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=X8UFBcRiUIg:5cHAjDn8V0A:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=X8UFBcRiUIg:5cHAjDn8V0A:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=X8UFBcRiUIg:5cHAjDn8V0A:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=X8UFBcRiUIg:5cHAjDn8V0A:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/X8UFBcRiUIg" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/open-source-makes-your-customers-happier</feedburner:origLink></item>
    <item>
      <pubDate>Wed, 04 Aug 2010 23:34:00 -0700</pubDate>
      <title>Goodbye Google Wave, Google, please open source it.</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/Pp2jFohtch4/goodbye-google-wave-google-please-open-source</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/goodbye-google-wave-google-please-open-source</guid>
      <description>&lt;p&gt;
	&lt;p&gt;I have just heard about the &lt;a href="http://googleblog.blogspot.com/2010/08/update-on-google-wave.html" target="_blank"&gt;Google Wave discontinuation&lt;/a&gt; by the end of the year, and I must say my feelings are mixed. For me, the real reason for it's failure is not user adoption like Google and others seem to put it, but mostly execution. &lt;p /&gt; &lt;a href="http://wave.google.com"&gt;Google Wave&lt;/a&gt; had a lot of technical hurdles, because it was very ambitious. For me the most promising part of the technology was the fact that &lt;a href="http://www.google.com"&gt;Google&lt;/a&gt; announced they would, at some time, open source the back-end server and let everyone, in their own infrastructure, install Wave servers, much in the same way that people install Mail servers. This is what was really great about Wave, not all the gadgets like real-time typing and correction. Because it meant that this technology would be truly de-centralised, that no one could "own" your information. Actually with the hindsight this was very strange coming from Google, who tries to get as much as people's data as they can in their infrastructure. Maybe this is the real reason they cancelled this project ? :) &lt;p /&gt; Anyway, at &lt;a href="http://www.jahia.org"&gt;Jahia&lt;/a&gt;, we initially were very skeptical about the technology, and to be frank, when we got our first accounts we didn't really know what to do with it. We had all kinds of ideas of how to integrate it with Jahia, and we played a lot with wavelets, but apart from the basic fun, we never found good use cases for it. Then suddenly one of our developers really insisted that we use it as a brainstorming tool, and we quickly discovered how great this new tool could be ! This was really the killer application for this type of usage, and despite some hurdles (no notifications at first, and lack of integration with browsers or desktop clients), we started using it regularly and were becoming quite good at it. &lt;p /&gt; So for us we really found a good way to use Google Wave and despite its flaws we were happy with it. And now Google has decided to cancel the project. Fine, we'll go back to our old ways of doing things, maybe having learned a little on how to better collaborate. &lt;p /&gt; I think that Google really has an opportunity now, at least if they are ready to take this chance, to fully open source the technology. Sure there might be some Google specific parts, or maybe even some missing parts, but both the &lt;a href="http://code.google.com/webtoolkit/"&gt;GWT&lt;/a&gt; client and server parts could be very interesting to a lot of developers, and some might even be able to use it as a basis for building libraries to implement the Wave protocol. They have already some source code available at the &lt;a href="http://www.waveprotocol.org/"&gt;Wave Protocol&amp;nbsp;website&lt;/a&gt; and they should just expand on that, make it into something easy to build and test locally, including the GWT client. &lt;p /&gt; I hope this is what they will do, and who knows, maybe this could even save Wave ?&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/goodbye-google-wave-google-please-open-source"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/goodbye-google-wave-google-please-open-source#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=Pp2jFohtch4:nflfjp-QI8k:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=Pp2jFohtch4:nflfjp-QI8k:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=Pp2jFohtch4:nflfjp-QI8k:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=Pp2jFohtch4:nflfjp-QI8k:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/Pp2jFohtch4" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/goodbye-google-wave-google-please-open-source</feedburner:origLink></item>
    <item>
      <pubDate>Thu, 29 Jul 2010 09:43:25 -0700</pubDate>
      <title>Thoughts on Adobe's planned acquisition of Day</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/yWiwx8L6_hs/thoughts-on-adobes-planned-acquisition-of-day</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/thoughts-on-adobes-planned-acquisition-of-day</guid>
      <description>&lt;p&gt;
	&lt;span style=""&gt;&lt;br /&gt;&lt;span&gt;As the web is still reacting to the news of Day's announced acquisition by Adobe, I couldn't help but also want to share my thoughts about this interesting new development in this arena.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;The first thing that comes to mind is a conflict of company ideologies. On one side a company that is built around a single product that uses a model of partly open source software, where all the infrastructure is open-sourced in Apache Software projects, and on the other a company that couldn't be more traditionally closed source.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;Which ideology will take over? At this point I think that no one can really tell. I believe that the deal was probably reached because Adobe made some medium-term commitment to keeping the same strategy in the business unit that Day will join, probably mostly in an effort not to scare away some of the most valuable open source contributors such as Roy Fielding or David Nueschler, and probably also because Adobe knows that it has some benefits to go in that direction.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;But if we look historically at acquisitions in this field, it takes a very real and very strong commitment to open source to stay the course. Even we, at Jahia, know and appreciate that. We distribute our own full code under the GPL license. Open source makes a lot of sense for a small company like ours, but for larger companies like Adobe the commitment is more difficult, because it is not entirely rational, it is also ideological. Some large companies, such as Google, partially use this as a recruiting tool, since researchers usually prefer the notion of sharing knowledge and having independent peer reviews than working alone.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;In a company like Adobe, or even Microsoft, to go the open source route usually takes some strong will from key company executives to happen. This has partially happened at Microsoft, which has now started contributing to the Apache Software Foundation. Other examples include Novell or IBM which were able to re-invent themselves by embracing open source.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;Coming back to Adobe, only time will tell if they will indeed commit to open source as a company in the long term. But I do think that it will be not be that easy for some Day employees to become part of a much larger structure that will change the way they have worked until now. This is true of any acquisition, not just this one. Hopefully they will help Adobe become a more open company.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;What does this all means for Jahia? Well many things. First of all it means that there is definitely great value in open source Java companies. It also validates the standard-based approach that has been a part of our software from the start. It means that customers that want a very agile relationship with their solution provider will probably be most likely to come to us rather than to Adobe. If Adobe doesn't commit in the long term to open source, we will benefit by offering a more open product, and if they do continue Day's strategy over the long term we will be able to collaborate with them to share and improve common infrastructure, technology and code. So I think that this is really good news for us all in all :)&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;So in conclusion, I would like to salute all my friends at Day, well done guys !&lt;/span&gt;&lt;br /&gt;&lt;/span&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/thoughts-on-adobes-planned-acquisition-of-day"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/thoughts-on-adobes-planned-acquisition-of-day#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=yWiwx8L6_hs:ljzngjHRy5Q:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=yWiwx8L6_hs:ljzngjHRy5Q:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=yWiwx8L6_hs:ljzngjHRy5Q:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=yWiwx8L6_hs:ljzngjHRy5Q:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/yWiwx8L6_hs" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/thoughts-on-adobes-planned-acquisition-of-day</feedburner:origLink></item>
    <item>
      <pubDate>Tue, 15 Sep 2009 07:20:00 -0700</pubDate>
      <title>Debugging EHCache in a cluster</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/NbX3gxIG2zo/debugging-ehcache-in-a-cluster</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/debugging-ehcache-in-a-cluster</guid>
      <description>&lt;p&gt;
	&lt;p&gt;Yesterday I had to find a bug in EHCache in a cluster installation, and wanted to use the EHCache remote debugger, as described here : &lt;a href="http://ehcache.org/documentation/remotedebugger.html"&gt;http://ehcache.org/documentation/remotedebugger.html&lt;/a&gt; &lt;br /&gt;&amp;nbsp;&lt;br /&gt;It turns out the documentation wasn't very clear, and it wasn't less clear was where the package could be found. In fact it can be retrieved here : &lt;a href="http://sourceforge.net/projects/ehcache/files/ehcache-debugger/"&gt;http://sourceforge.net/projects/ehcache/files/ehcache-debugger/&lt;/a&gt; (note the fact that it seems the name of the debugger is either "remote debugger" or "debugger", but it's the same code base). &lt;br /&gt;&amp;nbsp;&lt;br /&gt;Now the tricky part was to make it work with Jahia. The way the debugger works is to actually participate in the cluster as an EHCache cluster node. What the documentation doesn't tell you is that in order to participate in the cluster, it will need to be able to deserialize all the objects it receives in the cluster messages, and this is why your application JARs are required. Also, I have tested it with JGroups replication, and it seems to work fine, so it can safely be used in other setupts than the RMI replication. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;Another problematic part of the documentation is the fact that the example command line mixes the -classpath and -jar command line options, which isn't supported by the JDK 1.5. So the example command line from the documentation will not work. Also, as is the case with Jahia, there might be a lot of application JARs, so it can be quite tedious to list them all. I put a little shell script together, that will automatically create the classpath correctly for a Jahia installation, which I am showing here : &lt;br /&gt;&amp;nbsp;&lt;br /&gt;debug_ehcache.sh &lt;br /&gt;-------------------------- &lt;br /&gt; &lt;code&gt; &amp;nbsp;&lt;br /&gt;buildClassPath() { &lt;br /&gt;&amp;nbsp; jar_dir=$1 &lt;br /&gt;&amp;nbsp; if [ $# -ne 1 ]; then &lt;br /&gt;&amp;nbsp; echo "Jar directory must be specified." &lt;br /&gt;&amp;nbsp; exit 1 &lt;br /&gt;&amp;nbsp; fi &lt;br /&gt;&amp;nbsp; class_path= &lt;br /&gt;&amp;nbsp; c=1 &lt;br /&gt;&amp;nbsp; for i in `ls $jar_dir/*.jar` &lt;br /&gt;&amp;nbsp; do &lt;br /&gt;&amp;nbsp; if [ "$c" -eq "1" ]; then &lt;br /&gt;&amp;nbsp; class_path=${i} &lt;br /&gt;&amp;nbsp; c=2 &lt;br /&gt;&amp;nbsp; else &lt;br /&gt;&amp;nbsp; class_path=${class_path}:${i} &lt;br /&gt;&amp;nbsp; fi &lt;br /&gt;&amp;nbsp; done &lt;br /&gt;&amp;nbsp; echo $class_path &lt;br /&gt;&amp;nbsp; #return $class_path &lt;br /&gt;} &lt;br /&gt;JAHIA_LIBS=/Users/loom/java/deployments/jahia-6-0-hotfix/apache-tomcat-6.0.18/webapps/ROOT/WEB-INF/lib &lt;br /&gt;JAHIA_SHARED_LIBS=/Users/loom/java/deployments/jahia-6-0-hotfix/apache-tomcat-6.0.18/lib &lt;br /&gt;JAHIA_CLASSPATH=`buildClassPath ${JAHIA_LIBS}` &lt;br /&gt;JAHIA_SHARED_CLASSPATH=`buildClassPath ${JAHIA_SHARED_LIBS}` &lt;br /&gt;CLASSPATH=${JAHIA_CLASSPATH}:${JAHIA_SHARED_CLASSPATH}:./backport-util-concurrent-3.1.jar:./commons-logging-1.0.4.jar:./commons-collections-3.2.jar:./jsr107cache-1.0.jar:./ehcache-debugger-1.5.0.jar &lt;br /&gt;export CLASSPATH &lt;br /&gt;java net.sf.ehcache.distribution.RemoteDebugger ehcache-jahia_cluster.xml $1 $2 $3 $4 &lt;/code&gt; &lt;br /&gt;------------------- &lt;br /&gt;&amp;nbsp;&lt;br /&gt;Before launching this, make sure you copy your EHCache configuration file from WEB-INF/classes/ehcache-jahia_cluster.xml . Also, as this file uses variables injected from the jahia.properties file, you will have to replace the variables with the real values, as in the example below : &lt;br /&gt; &lt;code&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;cacheManagerPeerProviderFactory &lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp; class="net.sf.ehcache.distribution.jgroups.JGroupsCacheManagerPeerProviderFactory"&amp;nbsp;&amp;nbsp; properties="connect=TCP_NIO(start_port=7870;bind_addr=127.0.0.1;loopback=true;recv_buf_size=20000000;send_buf_size=640000;discard_incompatible_packets=true;max_bundle_size=64000;max_bundle_timeout=30;use_incoming_packet_handler=true;enable_bundling=true;use_send_queues=false;sock_conn_timeout=300;skip_suspected_members=true;use_concurrent_stack=true):&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; TCPPING(initial_hosts=127.0.0.1[7870],127.0.0.1[7871];port_range=10;timeout=3000;num_initial_members=2):&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; MERGE2(max_interval=100000;min_interval=20000):&lt;/p&gt;
&lt;p&gt;FD_SOCK:&lt;/p&gt;
&lt;p&gt;FD(timeout=10000;max_tries=5;shun=true):&lt;/p&gt;
&lt;p&gt;VERIFY_SUSPECT(timeout=1500):&lt;/p&gt;
&lt;p&gt;pbcast.NAKACK(gc_lag=100;retransmit_timeout=3000;discard_delivered_msgs=true):&lt;/p&gt;
&lt;p&gt;pbcast.STABLE:&lt;/p&gt;
&lt;p&gt;pbcast.GMS(join_timeout=5000;shun=true;print_local_addr=true):&lt;/p&gt;
&lt;p&gt;VIEW_SYNC(avg_send_interval=60000):&lt;/p&gt;
&lt;p&gt;FC(max_credits=2000000;min_threshold=0.10):&lt;/p&gt;
&lt;p&gt;FRAG2(frag_size=60000)"&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp; propertySeparator="::" /&amp;gt;&lt;/p&gt;
&lt;/code&gt;&lt;/p&gt;
&lt;p /&gt;
&lt;p&gt;You can then start using the script to listen to a cache in a Jahia cluster installation. Here is an example command line : &lt;br /&gt;&amp;nbsp; &lt;code&gt;&lt;br /&gt;./debug_ehcache.sh SkeletonCache &lt;br /&gt;&amp;nbsp;&lt;/code&gt;&lt;br /&gt;The output looks like this : &lt;br /&gt; &lt;code&gt;&amp;nbsp;&lt;br /&gt;Received removeAll notification. &lt;br /&gt;Cache: SkeletonCache Notifications received: 1 Elements in cache: 0 &lt;br /&gt;Cache: SkeletonCache Notifications received: 1 Elements in cache: 0 &lt;br /&gt;Cache: SkeletonCache Notifications received: 1 Elements in cache: 0 &lt;br /&gt;Received put notification for element [ key = 2-normal-en-administrators|administrators|guest|users-$$$#$#G_ContentPage_2WORKFLOWSTATE-normalLANGUAGECODE-en#$#G_SITE-2#$#G_USERNAME-administrators|administrators|guest|users, value=org.jahia.services.cache.CacheEntry@9d04dc, version=1, hitCount=0, CreationTime = 1252940741198, LastAccessTime = 0 ] &lt;br /&gt;Cache: SkeletonCache Notifications received: 2 Elements in cache: 1 &lt;br /&gt;Cache: SkeletonCache Notifications received: 2 Elements in cache: 1 &lt;br /&gt;Cache: SkeletonCache Notifications received: 2 Elements in cache: 1 &lt;br /&gt;Received put notification for element [ key = 2-normal-en-guest:0-$$$#$#G_ContentPage_2WORKFLOWSTATE-normalLANGUAGECODE-en#$#G_USERNAME-guest:0#$#G_SITE-2, value=org.jahia.services.cache.CacheEntry@8caee7, version=1, hitCount=0, CreationTime = 1252940747195, LastAccessTime = 0 ] &lt;br /&gt;Cache: SkeletonCache Notifications received: 3 Elements in cache: 2 &lt;br /&gt;Cache: SkeletonCache Notifications received: 3 Elements in cache: 2 &lt;br /&gt;Cache: SkeletonCache Notifications received: 3 Elements in cache: 2 &lt;br /&gt;Received put notification for element [ key = 302-normal-en-guest:0-$$$#$#G_USERNAME-guest:0#$#G_SITE-2#$#G_ContentPage_302WORKFLOWSTATE-normalLANGUAGECODE-en, value=org.jahia.services.cache.CacheEntry@535057, version=1, hitCount=0, CreationTime = 1252940754196, LastAccessTime = 0 ] &lt;br /&gt;&amp;nbsp; &lt;/code&gt;&lt;br /&gt;This can really be a neat tool to diagnose or simply get a feel of how Jahia is using EHCache to communicate within a cluster. I hope this little blog entry will help you use this debugger, because despite the tricky setup it is very useful and a neat design.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/debugging-ehcache-in-a-cluster"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/debugging-ehcache-in-a-cluster#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=NbX3gxIG2zo:fuuE22wxnA8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=NbX3gxIG2zo:fuuE22wxnA8:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=NbX3gxIG2zo:fuuE22wxnA8:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=NbX3gxIG2zo:fuuE22wxnA8:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/NbX3gxIG2zo" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/debugging-ehcache-in-a-cluster</feedburner:origLink></item>
    <item>
      <pubDate>Wed, 24 Jun 2009 08:35:00 -0700</pubDate>
      <title>The importance of standards</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/-5L6Gqvb3hc/the-importance-of-standards</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/the-importance-of-standards</guid>
      <description>&lt;p&gt;
	&lt;p&gt;I was going through some &lt;a href="http://en.wikipedia.org/wiki/Content_management_system" title="Wikipedia CMS definition" target="_blank"&gt;CMS&lt;/a&gt; and &lt;a href="http://en.wikipedia.org/wiki/Web_portal" title="Wikipedia Portal definition" target="_blank"&gt;portal&lt;/a&gt; software implementations yesterday, and looked at them from a standards point of view. You might wonder, why are standards important ? Isn't it easier to build something minimal that will do just the job ? Well in terms of software engineering it probably seems to be, but you end up in a very proprietary system, but using standards don't necessarily mean that you will have to build more code. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;One standard comparison that is often mentioned nowadays is the one between &lt;a href="http://en.wikipedia.org/wiki/SQL" title="SQL definition" target="_blank"&gt;SQL&lt;/a&gt; and &lt;a href="http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services" title="CMIS definition" target="_blank"&gt;CMIS&lt;/a&gt;. Some call CMIS the "SQL for content", while others (like my good colleague &lt;a href="stephanecroisier.jahia.com" title="St&amp;eacute;phane's blog" target="_blank"&gt;St&amp;eacute;phane&lt;/a&gt;) view it more as the SQL for file systems :) But anyway, what do these standards really bring us, except for the hassle of implementing them and even harder testing interoperability ? &lt;br /&gt;&amp;nbsp;&lt;br /&gt;I think one of the best examples in this area is what has happened in the browser world. They would have never existed if it wasn't for standards. When &lt;a href="http://www.mozilla.org" title="Mozilla home page" target="_blank"&gt;Mozilla&lt;/a&gt; was started, there wasn't really a standard for &lt;a href="http://en.wikipedia.org/wiki/HTML" title="Wikipedia HTML definition" target="_blank"&gt;HTML&lt;/a&gt;, it was written based on the implementation, but that's ok. When Mozilla became &lt;a href="http://en.wikipedia.org/wiki/Netscape" title="Wikipedia Netscape definition" target="_blank"&gt;Netscape&lt;/a&gt;, it added a lot of extensions to HTML, like layers, that weren't part of the standard, and when Internet Explorer came to the market, it had a different implementation of layers. So basically for a while, people building web sites either had to do two versions of their websites, or just refrain from using layers until they were standardized. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;So what did people gain from the standards ? Well on the end users part : choice. On the web developers side : less work. On the browser's side : a very good &lt;a href="http://en.wikipedia.org/wiki/API" title="Wikipedia API definition" target="_blank"&gt;API&lt;/a&gt; to implement and especially to test against ! The last point is very important, it is one of the reasons that Java became such a success. The API was clearly a "standard", established through the &lt;a href="http://jcp.org/en/home/index" title="Java Community Process home page" target="_blank"&gt;Java Community Process&lt;/a&gt; process, to make sure that various implementations would comply to the same API. Sure there were some glitches here and there, but globally it was quite a success. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;Giving customers choice is not necessarily something they will immediately understand, but it is good for them. When &lt;a href="http://www.microsoft.com/windows/internet-explorer/default.aspx" title="Internet Explorer home page" target="_blank"&gt;Internet Explorer&lt;/a&gt; became the dominant browser, the best way to attack it was through its less than compliant implementation of &lt;a href="http://www.w3.org/Style/CSS/" title="Cascading Style Sheets home page" target="_blank"&gt;CSS&lt;/a&gt;. Suddenly web developers starting complaining about high development costs, were developing better looking layouts on other browsers, and &lt;a href="http://www.mozilla.com/en-US/firefox/firefox.html" title="Mozilla Firefox home page" target="_blank"&gt;Firefox&lt;/a&gt; became a very strong competitor. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;In the CMS market, this need for standardization is still in the process of happening, but nonetheless important. Customers must understand that the investment they are doing into their content management system must imply the possibility to import and export the content easily, and especially interoperate between various content system. This is especially true when you go into the semantic web, where content systems will need to create semantic links across vendors, and that is still a bit of a pipe dream at this moment. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;Some standards are de-facto standards. When these de-facto standards are actually owned and controlled by a single company, this is more of a problem. Look for example at Microsoft's Internet Explorer or the &lt;a href="http://www.apple.com/iphone/apps-for-iphone/" title="iPhone AppStore home page" target="_blank"&gt;iPhone's AppStore&lt;/a&gt;. Both these de-facto standards are really creating frustration on both the user and developer's sides. In the &lt;a href="http://www.apple.com/iphone/" title="Apple iPhone home page" target="_blank"&gt;iPhone&lt;/a&gt;'s AppStore for example, the end-user cannot use applications that run in the background or fully interact with the phone, the applications only run on the iPhone or &lt;a href="http://www.apple.com/ipodtouch/" title="Apple's iPod Touch home page" target="_blank"&gt;iPod Touch&lt;/a&gt;, and any complaints are completely ignored by the company because it cannot handle the sheer volume of customer requests. On the developer's side, the closed platform means that you can spend 6 months developing an application that will never be accepted. Again the fact that a standard is de-facto doesn't guarantee it's success. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;But when the de-facto standard is established by an open-source foundation such as the &lt;a href="http://www.apache.org" title="Apache Software Foundation home page" target="_blank"&gt;Apache Foundation&lt;/a&gt;, things can be very different. Even in the case of &lt;a href="http://www.springsource.org" title="SpringSource's home page" target="_blank"&gt;SpringSource&lt;/a&gt;, fathers of the excellent Spring Framework, the de-facto standard can become a real strong force. So the combination of de-facto and open source is a really powerful one, especially if the implementation has a large public. But what is even better is a real standard and open-source implementations, like the &lt;a href="http://jackrabbit.apache.org/" title="Apache Jackrabbit project" target="_blank"&gt;Apache Jackrabbit&lt;/a&gt; or &lt;a href="http://incubator.apache.org/chemistry/" title="Apache Chemistry project" target="_blank"&gt;Apache Chemistry&lt;/a&gt; projects. Even if the project might still run out of steam one day, the standards on which they are based will still be there, and the legacy can be guaranteed to be understood and the interface still present to allow future developers to be able to interact with the systems. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;In the aviation industry, they do the exact opposite to what most of the software industry does, they only use "old" bricks, that they know have been proven to work, and adhere very strictly to standards and specifications. This allows constructors to protect human lives from harm. This has an incidence on cost of course, but because they are doing this mostly within a single company and also because of the materials and manpower needed. But there is software running in airplanes and space shuttles, so the importance of standards and high reliability doesn't need to be incompatible with the business of building software. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;The real hard part is building software quickly and reliably, without incurring too many costs, and this is where the open source community comes into play. Some projects in the Apache Foundation have been incredible in that regard. The &lt;a href="http://jackrabbit.apache.org/" title="Apache Jackrabbit home page" target="_blank"&gt;Apache Jackrabbit&lt;/a&gt; project is such an example, the &lt;a href="http://www.springsource.org/" title="Spring Framework home page" target="_blank"&gt;Spring Framework&lt;/a&gt; is another, and there are many such stories of high quality software, adhering to standards, that have been developed much quicker than ever before. But they wouldn't be interesting if they didn't adhere to a standard, be it de-facto (because of community size and open-source) or "real". &lt;br /&gt;&amp;nbsp;&lt;br /&gt;&lt;a href="http://www.jahia.org" title="Jahia's community home page" target="_blank"&gt;Jahia&lt;/a&gt; was born out of a proprietary content management system, and is moving all of it's sub-systems to be built on on top of both the "real" and de-facto standards. It builds value on top of bricks that have been proven to be reliable, modern and standard such as the &lt;a href="http://en.wikipedia.org/wiki/JSR-170" title="Wikipedia's JCR definition" target="_blank"&gt;JCR&lt;/a&gt;, the &lt;a href="http://jcp.org/en/jsr/detail?id=286" title="Portlet API 2.0 specification" target="_blank"&gt;Portlet API 2.0&lt;/a&gt;, &lt;a href="http://www.webdav.org/" title="WebDAV home page" target="_blank"&gt;WebDAV&lt;/a&gt;, &lt;a href="http://code.google.com/webtoolkit/" title="Google Web Toolkit home page" target="_blank"&gt;GWT&lt;/a&gt;, the Spring Framework, &lt;a href="http://logging.apache.org/log4j/" title="Log4J project" target="_blank"&gt;Log4J&lt;/a&gt;, and many more. We are working on integrating CMIS and possibly other new standards (such as the work being started in the &lt;a href="http://www.iks-project.eu/" title="IKS Project home page" target="_blank"&gt;IKS project&lt;/a&gt;). Of course the real value to the customer is not in the bricks, but in the building you have constructed using the bricks.&lt;/p&gt;

	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/the-importance-of-standards"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/the-importance-of-standards#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=-5L6Gqvb3hc:CVrT2b8PxPw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=-5L6Gqvb3hc:CVrT2b8PxPw:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=-5L6Gqvb3hc:CVrT2b8PxPw:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=-5L6Gqvb3hc:CVrT2b8PxPw:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/-5L6Gqvb3hc" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/the-importance-of-standards</feedburner:origLink></item>
    <item>
      <pubDate>Tue, 16 Jun 2009 00:25:00 -0700</pubDate>
      <title>On the subject of Jahia 6</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/jao5U2VYaW4/on-the-subject-of-jahia-6</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/on-the-subject-of-jahia-6</guid>
      <description>&lt;p&gt;
	&lt;p&gt;After the successful launch of Jahia 6, I'd like to take some time to give you a different perspective on what this version means to us. Basically, Jahia 6 was the beginning of a very interesting trend going on here : building on the experience and re-writing some of the older codebase. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;Jahia, the company, is now a little over 7 years old, and it has grown during all these years without having any external investors. So it has not always been easy, but the people that we have here are really amazing, and it is a real testament to all that we have achieved so much. You might not have heard much about us so far because we haven't been communicating much, but we intend to correct that now :) &lt;br /&gt;&amp;nbsp;&lt;br /&gt;Coming back to the codebase, you can accumulate a lot of code over 7 years, especially since the project started even before the company, and was bought-in when we started the business. I participated to the original codebase, and it is quite amazing to see how it has grown. Over the years, little by little, we have improved the software, adding features and making it faster. We have constantly worked to make it as easy to use as possible, and that is always a great challenge. This challenge is made even harder by all the browser incompatibilities. When Jahia was first written it had support for &lt;a href="http://en.wikipedia.org/wiki/Netscape#Netscape_Communicator_.28versions_4.0.E2.80.934.8.29" title="Netscape 4.7" target="_blank"&gt;Netscape 4.7&lt;/a&gt; and Internet Explorer 4 ! We basically had *very* different HTML for the two browsers then :) &lt;br /&gt;&amp;nbsp;&lt;br /&gt;Jahia 6 was a great project, because we decided to take huge leaps instead of smaller steps this time. Despite this, we didn't compromise on quality nor performance and constantly had the aim that this version should be one of the best ever, and of course you be the judge but I think we did quite well. Jahia 6 introduces major platform changes : new content definitions based on the standard &lt;a href="http://jackrabbit.apache.org/node-type-notation.html" title="CND format" target="_blank"&gt;JSR-170 CND&lt;/a&gt; format, completely new file repository based on &lt;a href="http://jcp.org/en/jsr/detail?id=170" title="JCR" target="_blank"&gt;JSR-170&lt;/a&gt;, connectors to all kinds of repositories, complete rewrite of the &lt;a href="http://en.wikipedia.org/wiki/Ajax_(programming)" title="AJAX" target="_blank"&gt;AJAX&lt;/a&gt; framework using &lt;a href="http://code.google.com/webtoolkit/" title="GWT" target="_blank"&gt;GWT&lt;/a&gt;, lots of improvements on our templating in order to make it easy for integrators to work fast, using re-usable blocks. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;The new version expands on one of Jahia's biggest strengths, the tight integration of CMS and portal features. In Jahia 5, you could easily include content objects and &lt;a href="http://en.wikipedia.org/wiki/Portlet" title="Portlet definition" target="_blank"&gt;portlets&lt;/a&gt; on the same page, and in Jahia 6 you can not only continue to do this, but also use &lt;a href="http://en.wikipedia.org/wiki/Mashup_(web_application_hybrid)" title="Mashup definition" target="_blank"&gt;mashups&lt;/a&gt; (think of "Javascript portlets") interchangeably with JSR-168 portlets. Actually we went further than that and directly included support for the brand new &lt;a href="http://jcp.org/en/jsr/detail?id=286" title="Portlet API 2.0 specification" target="_blank"&gt;portlet API 2.0 standard&lt;/a&gt; , which adds support for inter-portlet event communication and other niceties. We support both &lt;a href="http://en.wikipedia.org/wiki/Mashup_(web_application_hybrid)" title="Mashup definition" target="_blank"&gt;mashups&lt;/a&gt; and portlets because we moved the portlet instance data into the content repository, and so we can easily reference both front-end code (HTML + Javascript) or a reference to a portlet deployed in Jahia. Upon page rendering, Jahia simply resolves the content to be displayed, either extracting the mashup from the repository, or dispatching to the portlet to get it's view. This is of course completely transparent to the end user, who can then simply re-use block elements inside a page, should they be portlets or mashups. We have also added the possibility to deploy portlets inside the same context as Jahia, making it possible to access all of Jahia's API from within a portlet. We have used this feature ourselves to build our RSS portlet, that comes packaged with Jahia 6. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;On the front-end side, I think that a lot of users will enjoy a new feature we call "inline editing". It allows you to simply click on the text you want to modify, and directly modify it right on the page. This makes it so intuitive you'd like everything to work that way :) This new feature requires users to use Safari 3, Firefox 3 or Internet Explorer 6+, since it uses a feature originally introduced by Microsoft and then included by others. &lt;br /&gt;&amp;nbsp;&lt;br /&gt;I sincerely hope you will enjoy Jahia 6 as much as we enjoyed working on it. Don't hesitate to &lt;a href="http://www.jahia.com/jahia/Jahia/site/jahiacom/download" title="Jahia 6 EE download link" target="_blank"&gt;download it&lt;/a&gt;, or &lt;a href="http://demo.jahia.org/cms" title="Jahia online demo" target="_blank"&gt;test it on our online demo&lt;/a&gt;. Please don't hesitate to let us know what you think about it, either by commenting on this blog or through our &lt;a href="http://www.jahia.org/forum/" title="Jahia Forums" target="_blank"&gt;public forums&lt;/a&gt;.&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/on-the-subject-of-jahia-6"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/on-the-subject-of-jahia-6#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=jao5U2VYaW4:nAJmsFWRKCw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=jao5U2VYaW4:nAJmsFWRKCw:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=jao5U2VYaW4:nAJmsFWRKCw:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=jao5U2VYaW4:nAJmsFWRKCw:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/jao5U2VYaW4" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/on-the-subject-of-jahia-6</feedburner:origLink></item>
    <item>
      <pubDate>Thu, 14 May 2009 03:25:00 -0700</pubDate>
      <title>IE 6 not supported in SharePoint 2010, even Microsoft likes Safari :)</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/UTTiSRhfgp8/ie-6-not-supported-in-sharepoint-2010-even-mi</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/ie-6-not-supported-in-sharepoint-2010-even-mi</guid>
      <description>&lt;p&gt;
	&lt;p&gt;At Jahia, we constantly run into the problem of IE 6 support, which (unfortunately) is still a requirement for us. But I couldn't suppress a huge smile when the following excerpt from &lt;a href="http://blogs.zdnet.com/microsoft/?p=2761"&gt;this page&lt;/a&gt; : &lt;br /&gt;
&lt;a href="http://blogs.msdn.com/sharepoint/archive/2009/05/07/announcing-sharepoint-server-2010-preliminary-system-requirements.aspx"&gt;SharePoint Server 2010 won’t support Internet Explorer 6&amp;lt;&lt;/a&gt;. From the SharePoint Team blog: SharePoint 2010 will be “targeting standards based browsers (XHTML 1.0 compliant) including Internet Explorer 7, Internet Explorer 8 and Firefox 3.x. running on Windows Operating Systems. In addition we’re planning on &lt;a href="http://blogs.msdn.com/sharepoint/archive/2009/05/07/announcing-sharepoint-server-2010-preliminary-system-requirements.aspx"&gt;an increased level of compatibility with Firefox 3.x and Safari 3.x&lt;/a&gt; on non-Windows Operating Systems,” according to the SharePoint Team Blog."&lt;br /&gt;
So basically even Microsoft is not phasing out IE 6 support and improving compatibility with Safari ! I love the "targeting standards based browsers", clearly implying that IE 6 is far from it, which I think nobody in their right mind will contest.&lt;br /&gt;
The real problem is that according to a &lt;a href="http://news.cnet.com/8301-17939_109-10231713-2.html"&gt;Forrester Research report&lt;/a&gt;, IE 6 still has a 60% market share in the enterprise. I believe that the only real way that we can get this situation to change is for companies to introduce a browser policy, and to possibly use Firefox as the "new browser", and whatever version of IE is required for "legacy applications". But the reality is that IE 6 must die, and if the newer versions of IE are not interesting enough, then users should switch to other implementations, like Firefox, Safari or Chrome.&lt;br /&gt;
Another interesting point, although less surprising, is that CMIS is confirmed for the next version of SharePoint.&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/ie-6-not-supported-in-sharepoint-2010-even-mi"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/ie-6-not-supported-in-sharepoint-2010-even-mi#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=UTTiSRhfgp8:VpUeNX_BGKg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=UTTiSRhfgp8:VpUeNX_BGKg:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=UTTiSRhfgp8:VpUeNX_BGKg:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=UTTiSRhfgp8:VpUeNX_BGKg:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/UTTiSRhfgp8" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/ie-6-not-supported-in-sharepoint-2010-even-mi</feedburner:origLink></item>
    <item>
      <pubDate>Mon, 11 May 2009 23:38:22 -0700</pubDate>
      <title>AtomPub a failure ? No, just not as good as JSON :)</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/HtBbRO4RZyc/atompub-a-failure-no-just-not-as-good-as-json</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/atompub-a-failure-no-just-not-as-good-as-json</guid>
      <description>&lt;p&gt;
	&lt;div&gt;I found a very interesting blog post by Joe Gregorio entitled&amp;nbsp;&lt;a href="http://bitworking.org/news/425/atompub-is-a-failure"&gt;AtomPub is a failure&lt;/a&gt;. Well of course the title is there to get your attention, but the underlying argument is interesting : we now have other options for interchange formats.&lt;/div&gt;&lt;div&gt;We&amp;nbsp;definitely&amp;nbsp;live in interesting times, where so much focus on ease of integration is moving interoperability a *lot* faster. This can be a problem for standards that are trying to keep up, and mostly why I strongly believe that it can be a good thing implementation can drive specification like in the case of&amp;nbsp;&lt;a href="http://incubator.apache.org/chemistry/"&gt;Apache Chemistry&lt;/a&gt;, the Apache project to build a strong&amp;nbsp;&lt;a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis"&gt;CMIS&lt;/a&gt;&amp;nbsp;implementation. Standards are very important, but in the end people also want and need strong reference implementations of those standards. After all, even&amp;nbsp;&lt;a href="http://www.ietf.org/rfc/rfc2616.txt"&gt;HTTP&lt;/a&gt;&amp;nbsp;was specified together with it's first implementation :)&lt;/div&gt;&lt;div&gt;&lt;a href="http://www.json.org/"&gt;JSON&lt;/a&gt;&amp;nbsp;is incredibly powerful because it is so simple. I can explain it to a junior developer in a few minutes. I have trouble discussing&amp;nbsp;&lt;a href="http://www.w3.org/XML/"&gt;XML&lt;/a&gt;&amp;nbsp;formats with senior developers. Sure JSON is not as complete, but it also serves a lot of purposes. Don't get me wrong, I'm not saying that we must get rid of XML, it is here to stay and quite useful, but I'm mostly talking about simplicity.&lt;/div&gt;&lt;div&gt;Another aspect of JSON that most tend to ignore is that with it's simplicity also comes it's efficiency. It is very hard to find another interchange format that is more compact, and easier to parse. In web systems that are constantly trying to handle bigger loads, the cost of XML processing can be offset by using JSON.&lt;/div&gt;&lt;div&gt;A really hope that the CMIS committee will approve the upcoming proposal to introduce JSON as a binding, even if it means in a first version to use it as an AtomPub interchange format, but I would much prefer that they go the whole way of making it an extremely simple binding that can be implemented by many in very little time. They have so far had this focus, so I'm pretty sure they are interested in this idea.&lt;/div&gt;&lt;div&gt;Oh and yes I am thinking about joining the&amp;nbsp;&lt;a href="http://www.oasis-open.org"&gt;OASIS&lt;/a&gt;&amp;nbsp;TC :)&lt;/div&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/atompub-a-failure-no-just-not-as-good-as-json"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/atompub-a-failure-no-just-not-as-good-as-json#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=HtBbRO4RZyc:09YAro5gWbU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=HtBbRO4RZyc:09YAro5gWbU:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=HtBbRO4RZyc:09YAro5gWbU:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=HtBbRO4RZyc:09YAro5gWbU:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/HtBbRO4RZyc" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/atompub-a-failure-no-just-not-as-good-as-json</feedburner:origLink></item>
    <item>
      <pubDate>Thu, 07 May 2009 00:16:00 -0700</pubDate>
      <title>Will CMIS get a JSON binding ?</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/E1dqJUe4SWI/will-cmis-get-a-json-binding</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/will-cmis-get-a-json-binding</guid>
      <description>&lt;p&gt;
	&lt;p&gt;During the &lt;a href="http://dev.day.com/microsling/content/blogs/main/cmisplugfest.html" title="CMIS PlugFest initial invitation" target="_blank"&gt;CMIS PlugFest&lt;/a&gt;, an idea that was mentioned by a few participants consisted of using &lt;a href="http://www.json.org/" title="JSON Specification" target="_blank"&gt;JSON&lt;/a&gt; as a transport mechanism for &lt;a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis" title="CMIS Specification" target="_blank"&gt;CMIS&lt;/a&gt; repository operations. The idea was to be able to easily develop thin clients such as Javascript or PHP clients, and avoiding the pains of generating or parsing XML data. &lt;br /&gt;I think this might potentially be the "revolutionary" binding in the specification, that really has the potential to surpass all the others over time. Sure it is absolutely great (and at the same time a double-edge sword since it means more work for implementors) that CMIS has all these bindings for a first version, but I think that we will eventually see a natural selection where only the easiest to integrate with all technologies will survive. &lt;br /&gt;It takes one line of &lt;a href="http://www.php.net/" title="PHP" target="_blank"&gt;PHP&lt;/a&gt; (5.2) to serialize/deserialize JSON data (&lt;a href="http://ch.php.net/manual/en/function.json-encode.php" title="PHP json_encode function" target="_blank"&gt;json_encode&lt;/a&gt;), and there are high quality libraries available for all the modern languages out there. Personally I've implemented JSON for an iPhone application in Objective C and it proved to be the most efficient way of transferring &lt;a href="http://en.wikipedia.org/wiki/UTF-8" title="UTF-8" target="_blank"&gt;UTF-8&lt;/a&gt; data over the wire. &lt;br /&gt;The hard part of course is that JSON does not specify structure, only serialization format, and therefore it would be very important that the CMIS specification strongly describe the structure of the JSON payloads that are going back and forth between the client and the server. &lt;br /&gt;JSON handles complex serialization a lot more elegantly than SOAP web services, and is simple enough for anyone to understand in a matter of minutes. Wouldn't that be a great basis for the content management interoperability standard ? &lt;br /&gt;I know that a few people involved in the CMIS specification are already hard at work on proposing JSON as a binding for the 1.0 specification. This will be tricky since the deadline for the approval of the specification cannot change, so it means that all this must happen without slowing down the rest of the work. This will be a challenge, but I'm really interested in helping out, so please let me know how :) &lt;br /&gt;I dream of a world where I can directly interface a lightweight Javascript CMIS client with any CMIS compliant server. My mind is racing with the possibilities...&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/will-cmis-get-a-json-binding"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/will-cmis-get-a-json-binding#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=E1dqJUe4SWI:kyU8Xa_7CSQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=E1dqJUe4SWI:kyU8Xa_7CSQ:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=E1dqJUe4SWI:kyU8Xa_7CSQ:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=E1dqJUe4SWI:kyU8Xa_7CSQ:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/E1dqJUe4SWI" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/will-cmis-get-a-json-binding</feedburner:origLink></item>
    <item>
      <pubDate>Mon, 04 May 2009 23:30:00 -0700</pubDate>
      <title>Unlocking the full potential of Apache Chemistry : C++, C#, PHP, Javascript, (insert your favorite language here)</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/1CHGw-DpYgg/unlocking-the-full-potential-of-apache-chemis</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/unlocking-the-full-potential-of-apache-chemis</guid>
      <description>&lt;p&gt;
	&lt;div&gt;The &lt;a href="http://incubator.apache.org/chemistry/" title="Apache Chemistry project" target="_blank"&gt;Apache Chemistry&lt;/a&gt; project, the incubator project that was just approved has an incredible potential. Started as a place to experiment with a Java implementation of the &lt;a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis" title="CMIS Specification" target="_blank"&gt;CMIS&lt;/a&gt; specification, it can become much more. There are already implementations out there in Javascript and C++, although not yet contributed to the project, but this might happen sooner than you think.&lt;/div&gt;&lt;div&gt;The hardest thing to do is to achieve in any standard is true interoperability. But what if everyone was using the same code base from the&lt;a href="http://www.apache.org" title="Apache Foundation website" target="_blank"&gt; Apache Foundation&lt;/a&gt;, freely available to businesses ? What if all this code was fully tested by automated integration test matrixes ? Even achieving this is a challenge in itself but it is possible, and I really think it should happen. My dream, although probably unrealistic is that even major vendors such as Microsoft, IBM &amp;amp; EMC could use the code developed in Chemistry as the basis for their CMIS implementation, and contribute back to the project whenever they see problems.&lt;/div&gt;&lt;div&gt;A lot of what is happening with CMIS is reminiscent of the &lt;a href="http://en.wikipedia.org/wiki/SOAP" title="SOAP Wikipedia definition" target="_blank"&gt;SOAP&lt;/a&gt; craze. After all SOAP is used as a binding for CMIS, so it is quite normal to see similarities. One of the biggest interoperability problems for SOAP lied in the potentially complex serialization of custom objects, and this proved in real life to be very difficult to get to work between implementations. It is a testament to the great work of the contributors to the Apache projects related to SOAP implementations (&lt;a href="http://ws.apache.org/axis2/" title="Apache Axis 2" target="_blank"&gt;Axis&lt;/a&gt;, and before that Apache SOAP) that you could get web services to really talk to each other.&lt;/div&gt;&lt;div&gt;The Apache foundation is the perfect place for such standards to be implemented and grow as the basis for the network infrastructure of the entire industry. It is a place where even competing interests can find common ground for sharing development costs.&lt;/div&gt;&lt;div&gt;Of course it's not necessarily easy to directly use Apache-licensed code inside corporations such as Microsoft or IBM, as they are very concerned about code auditing, especially as they are often the target of copyright infringement lawsuits, but at least IBM is known to use such code, and in some cases simply packaging Apache products (such as the IBM HTTP Server). So we know that even if it is not trivial to achieve it is possible. And for Microsoft, well maybe this will convince you ? &lt;a href="http://port25.technet.com/archive/2008/07/25/oscon2008.aspx"&gt;http://port25.technet.com/archive/2008/07/25/oscon2008.aspx&lt;/a&gt;&lt;/div&gt;&lt;div&gt;I'm dreaming of an Apache Chemistry project with the following implementations available to all : Java, PHP, C#, C++, Javascript. Then of course you could have more such as Ruby, Python or whatever else you love, but the initial list would be perfect for integration with most systems, and provide truly interoperable systems, not just at the specification level, but truly at the implementation level.&lt;/div&gt;&lt;div&gt;Maybe it's just a pipe dream, but it &lt;b&gt;is&lt;/b&gt; possible, so maybe we should get together and try ?&lt;/div&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/unlocking-the-full-potential-of-apache-chemis"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/unlocking-the-full-potential-of-apache-chemis#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=1CHGw-DpYgg:Xmhsgs0JBpo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=1CHGw-DpYgg:Xmhsgs0JBpo:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=1CHGw-DpYgg:Xmhsgs0JBpo:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=1CHGw-DpYgg:Xmhsgs0JBpo:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/1CHGw-DpYgg" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/unlocking-the-full-potential-of-apache-chemis</feedburner:origLink></item>
    <item>
      <pubDate>Sun, 03 May 2009 23:28:00 -0700</pubDate>
      <title>CMIS PlugFest interoperability demo videos</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/DoYbq8-Ponc/cmis-plugfest-interoperability-demo-videos</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/cmis-plugfest-interoperability-demo-videos</guid>
      <description>&lt;p&gt;
	&lt;p&gt;While at the &lt;a href="http://dev.day.com/microsling/content/blogs/main/cmisplugfest.html" title="CMIS PlugFest invitation"&gt;CMIS PlugFest&lt;/a&gt; held in Basel (Switzerland) in April 2009, I managed to quickly get my Flip out to record some videos of the demonstrations of the interoperability between client and servers. The videos you will see here are organised by CMIS client implementations. Please excuse the low quality of the audio and the sometimes difficult to read screens, I hadn't planned to do this but I thought it might still be interesting to watch for all that weren't present. I highly recommend, if you have the bandwidth, that you view the videos in HD, it will be easier to read the screens. &lt;br /&gt;So here are the videos : &lt;br /&gt; &lt;br /&gt;SourceSense CMIS Portlet client &lt;br /&gt;&lt;object height="417" width="500"&gt;&lt;param name="movie" value="http://www.youtube.com/v/zynOPrrfZD8&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" /&gt;&lt;param name="wmode" value="transparent" /&gt;&lt;embed src="http://www.youtube.com/v/zynOPrrfZD8&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" wmode="transparent" type="application/x-shockwave-flash" height="417" width="500" /&gt;&lt;/object&gt; &lt;br /&gt; &lt;br /&gt;Flex CMIS Explorer &lt;br /&gt;&lt;object height="417" width="500"&gt;&lt;param name="movie" value="http://www.youtube.com/v/e8hzZ8PXm0s&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" /&gt;&lt;param name="wmode" value="transparent" /&gt;&lt;embed src="http://www.youtube.com/v/e8hzZ8PXm0s&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" wmode="transparent" type="application/x-shockwave-flash" height="417" width="500" /&gt;&lt;/object&gt; &lt;br /&gt; &lt;br /&gt;Javascript Chemistry CMIS client &lt;br /&gt;&lt;object height="417" width="500"&gt;&lt;param name="movie" value="http://www.youtube.com/v/Mz3nHWrY0bw&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" /&gt;&lt;param name="wmode" value="transparent" /&gt;&lt;embed src="http://www.youtube.com/v/Mz3nHWrY0bw&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" wmode="transparent" type="application/x-shockwave-flash" height="417" width="500" /&gt;&lt;/object&gt; &lt;br /&gt; &lt;br /&gt;Alfresco JUnit CMIS Testsuite &lt;br /&gt;&lt;object height="417" width="500"&gt;&lt;param name="movie" value="http://www.youtube.com/v/p84_n7zpGL4&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" /&gt;&lt;param name="wmode" value="transparent" /&gt;&lt;embed src="http://www.youtube.com/v/p84_n7zpGL4&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" wmode="transparent" type="application/x-shockwave-flash" height="417" width="500" /&gt;&lt;/object&gt; &lt;br /&gt; &lt;br /&gt;OpenText Windows CMIS integration &lt;br /&gt;&lt;object height="417" width="500"&gt;&lt;param name="movie" value="http://www.youtube.com/v/cG1s9qSHYIM&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" /&gt;&lt;param name="wmode" value="transparent" /&gt;&lt;embed src="http://www.youtube.com/v/cG1s9qSHYIM&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" wmode="transparent" type="application/x-shockwave-flash" height="417" width="500" /&gt;&lt;/object&gt; &lt;br /&gt; &lt;br /&gt;SAP ECM Explorer CMIS plug-in &lt;br /&gt;&lt;object height="417" width="500"&gt;&lt;param name="movie" value="http://www.youtube.com/v/Kj9T4mqWsMg&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" /&gt;&lt;param name="wmode" value="transparent" /&gt;&lt;embed src="http://www.youtube.com/v/Kj9T4mqWsMg&amp;amp;rel=1&amp;amp;ap=%2526fmt%3D18" wmode="transparent" type="application/x-shockwave-flash" height="417" width="500" /&gt;&lt;/object&gt; &lt;br /&gt; &lt;br /&gt;Unfortunately I don't have a video of myself (I was first to talk and it's kind of awkward to talk and take of video of yourself :)) talking about the integration I wrote during the CMIS PlugFest, but what I said was mostly that it could connect and navigate both the Jackrabbit Chemistry and Alfresco repositories. It is a goal for &lt;a href="http://www.jahia.com" title="Jahia WCM with portal and dms features" target="_blank"&gt;Jahia&lt;/a&gt; to work with &lt;a href="http://wiki.apache.org/incubator/ChemistryProposal" title="Apache Chemistry proposal" target="_blank"&gt;Apache Chemistry&lt;/a&gt; to be able to talk to CMIS repositories, and also expose it's own repository through Apache Chemistry. &lt;br /&gt;Let me know if you thought these videos were helpful, I might make some more regularly in that case.&lt;/p&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/cmis-plugfest-interoperability-demo-videos"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/cmis-plugfest-interoperability-demo-videos#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=DoYbq8-Ponc:xRC4HijGctU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=DoYbq8-Ponc:xRC4HijGctU:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=DoYbq8-Ponc:xRC4HijGctU:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=DoYbq8-Ponc:xRC4HijGctU:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/DoYbq8-Ponc" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/cmis-plugfest-interoperability-demo-videos</feedburner:origLink></item>
    <item>
      <pubDate>Fri, 01 May 2009 02:51:00 -0700</pubDate>
      <title>CMIS PlugFest : Day 2</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/L2x5JKIskkc/cmis-plugfest-day-2</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/cmis-plugfest-day-2</guid>
      <description>&lt;p&gt;
	&lt;div&gt;The second day of the &lt;a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis" title="OASIS CMIS Specification" target="_blank"&gt;CMIS&lt;/a&gt; PlugFest was less about setting things up than actually trying to fill the grid of possible tests (over 28 possible tests) that cover all the combinations of client and server implementations that were available there.&lt;/div&gt;
&lt;div&gt;I was myself hacking most of the day to get a brand new CMIS client implementation up and running, and I got the first unit tests working against both the Alfresco CMIS server and the Day CRX server. I even managed to navigate through the whole repositories. I then went on to work on the integration with Jahia, to be able to browse those repositories directly from Jahia's file manager. Unfortunately, despite the amount of code that was produced in the last 24 hours, it just wasn't possible. Despite this I believe this is really close to happening, and we should have something experimental to test against the various servers quite soon.&lt;/div&gt;
&lt;div&gt;The good news of the day came from Jukka Zitting that was visiting the PlugFest, and that announced that &lt;a href="http://wiki.apache.org/incubator/ChemistryProposal" title="Apache Chemistry" target="_blank"&gt;Apache Chemistry&lt;/a&gt; was officially accepted by the Apache Foundation as an incubator project, and so over the course of the week-end Florent Guillaume, from Nuxeo, who contributed most of the code for Chemistry, will finally be able to commit all this work and let the community hack away at it.&lt;/div&gt;
&lt;div&gt;We were also joined during the day by IBM who was also providing a server against which to test. We had very interesting discussions about what was needed in the CMIS specification. A few of us believed that CMIS should really make usage of &lt;a href="http://www.json.org/" title="JSON" target="_blank"&gt;JSON&lt;/a&gt;, and it seems that a proposal for going in that direction might just happen, but it must happen fast, as there is a lot of pressure to get CMIS 1.0 out the door soon.&lt;/div&gt;
&lt;div&gt;The idea behind using JSON with CMIS is quite a natural one. Why have to deal with all the XML parsing involved in Atom Pub and Web services when you could use the extremely simple JSON format to exchange all the data you need ? I really hope that this will be added to CMIS as this could make it one of it's most flexible bindings. It is much simple to develop lightweight CMIS clients without the need for XML parsing. I'm mostly thinking of PHP, Javascript and other technologies.&lt;/div&gt;
&lt;div&gt;In the interoperability tests, search was still a problem for many clients and servers, and this was of course expected as it is the most complex part to implement. This also means that it will be necessary in the near future to perform another interoperability PlugFest to go further into the testing and make sure that even search works properly.&lt;/div&gt;
&lt;div&gt;The day was concluded with demonstrations of a few combinations of client and servers. Among the demonstrated clients were : Chemistry Javascript against Day CRX + Chemistry, SourceSense's CMIS Portlet against Alfresco, the CMIS Flex Explorer against Alfresco (which was also the client that worked against most of the servers !), OpenText's C++/Java client that integrates with Windows Explorer, Outlook and MS Word, and last but not least SAP's client that plugs into an existing infrastructure of explorer tools that plug into various SAP backend repositories (CMIS or not) and also exposes all the various back ends as WebDAV resources. This made me smile because there has been a lot of discussion wether CMIS should have a WebDAV binding, and basically SAP was demonstrating WebDAV on top of CMIS :)&lt;/div&gt;
&lt;div&gt;During the demonstrations, a lot of discussions were focused on making sure that the points that were problematic to implementors were noted and then discussed in the OASIS TC. Among those points were the upload mechanism of binary data that is not very clear when using the Atom Pub binding, because there are two ways of doing this, and therefore this is confusing to client implementors. The second point concerned path navigation, and the fact that CMIS currently doesn't offer a way to lookup a content object by it's path. Currently, when given a path, the CMIS client implementations must navigate from the parent path down to all the descendants to find the object corresponding to the path, which is not very speed efficient.&lt;/div&gt;
&lt;div&gt;It will be very interesting to see if these points can be adressed efficiently to avoid side tracking the specification. It seems that major vendors such as IBM, Microsoft and EMC want CMIS to be completed in Q3 2009, so this doesn't leave much time to solve issues.&lt;/div&gt;
&lt;div&gt;All in all, I'd like to thank Day for hosting this PlugFest. This event, although not too certain how it would happen initially, turned out to be really necessary, and gave a really good picture of the real state of the CMIS interoperability. It is certain that this must happen again, when implementations are more mature, and especially when Apache Chemistry is fully available and ready to be tested. I would also like to thank Dave Caruana (Alfresco), who has been really great, helping me out with getting my tests up and running.&lt;/div&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/cmis-plugfest-day-2"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/cmis-plugfest-day-2#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=L2x5JKIskkc:4hyDzJNk9ho:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=L2x5JKIskkc:4hyDzJNk9ho:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=L2x5JKIskkc:4hyDzJNk9ho:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=L2x5JKIskkc:4hyDzJNk9ho:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/L2x5JKIskkc" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/cmis-plugfest-day-2</feedburner:origLink></item>
    <item>
      <pubDate>Thu, 30 Apr 2009 01:07:18 -0700</pubDate>
      <title>CMIS PlugFest : Day 1</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/Q9AHLv8MkqA/cmis-plugfest-day-1</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/cmis-plugfest-day-1</guid>
      <description>&lt;p&gt;
	I&amp;#39;m currently in Basel, participating in the CMIS PlugFest. For those of you that are not familiar with CMIS, you might think of it to content management (well mostly document management right now, but that might change) as is SQL to databases. It is a standard that will hopefully help interoperability between content management systems.&lt;div&gt;
Day 1 started with some informal introductions, and setup of the existing servers. We now have OpenText, Alfresco and Jackrabbit+Chemistry servers up and running, and are running interoperability tests against those using a variety of clients, including OpenText that has a C++ plugin that connects Windows Explorer and as well as Office tools to CMIS back ends, SAP, Alfresco test units, two Flex-based clients (CMIS Explorer and CMIS Spaces), a Apache Chemistry CMIS Javascript client written by David Nuescheler at Day, an Apache Chemistry Java client that Florent Guillaume (Nuxeo software) is working hard on to commit hopefully before the end of the week.&lt;/div&gt;
&lt;div&gt;It&amp;#39;s really great to see so much effort going into interoperability tests. The most interesting thing about CMIS is the momentum behind it, more than the technology, that will probably still evolve over the year. It is also very important to get the first version of the specification out as early as possible, because so many specifications fall into tech-limbo, to never be completed (802.11n, etc...).&lt;/div&gt;
&lt;div&gt;Apache Chemistry is also looking better than ever, having just been accepted into the incubator at Apache, and the code will probably be committed over the week-end. From then on hopefully the community will be able to have a look at it. This will also help interoperability, as even major vendors could use this code base to ensure compatibility.&lt;/div&gt;
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/cmis-plugfest-day-1"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/cmis-plugfest-day-1#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=Q9AHLv8MkqA:REUCZ3cFtLE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=Q9AHLv8MkqA:REUCZ3cFtLE:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=Q9AHLv8MkqA:REUCZ3cFtLE:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=Q9AHLv8MkqA:REUCZ3cFtLE:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/Q9AHLv8MkqA" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/cmis-plugfest-day-1</feedburner:origLink></item>
    <item>
      <pubDate>Thu, 30 Apr 2009 00:00:18 -0700</pubDate>
      <title>A new blog</title>
      <link>http://feedproxy.google.com/~r/jahia/serge/~3/sCb3D44hgLE/a-new-blog-6</link>
      <guid isPermaLink="false">http://sergehuber.jahia.com/a-new-blog-6</guid>
      <description>&lt;p&gt;
	I will post here thoughts and news about the technology that we are looking at while developing Jahia, and keep you up to date on what is going on both internally and exernally.
	
&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sergehuber.jahia.com/a-new-blog-6"&gt;Permalink&lt;/a&gt; 

	| &lt;a href="http://sergehuber.jahia.com/a-new-blog-6#comment"&gt;Leave a comment&amp;nbsp;&amp;nbsp;&amp;raquo;&lt;/a&gt;

&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=sCb3D44hgLE:cwVLtgfIz3E:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=sCb3D44hgLE:cwVLtgfIz3E:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/jahia/serge?a=sCb3D44hgLE:cwVLtgfIz3E:-BTjWOF_DHI"&gt;&lt;img src="http://feeds.feedburner.com/~ff/jahia/serge?i=sCb3D44hgLE:cwVLtgfIz3E:-BTjWOF_DHI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/jahia/serge/~4/sCb3D44hgLE" height="1" width="1"/&gt;</description>
      <posterous:author>
        <posterous:userImage>http://files.posterous.com/user_profile_pics/57606/me_in_suit_943x943.jpg</posterous:userImage>
        <posterous:profileUrl>http://posterous.com/users/1m6FwGSiVnb</posterous:profileUrl>
        <posterous:firstName>Serge</posterous:firstName>
        <posterous:lastName>Huber</posterous:lastName>
        <posterous:nickName>bhillou</posterous:nickName>
        <posterous:displayName>Serge Huber</posterous:displayName>
      </posterous:author>
    <feedburner:origLink>http://sergehuber.jahia.com/a-new-blog-6</feedburner:origLink></item>
  </channel>
</rss>

