<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Liferay: Good, Bad or Ugly?</title>
	<atom:link href="http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=liferay-good-bad-or-ugly</link>
	<description>A day in the life of a developer</description>
	<lastBuildDate>Wed, 21 Jul 2010 14:26:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jake</title>
		<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/comment-page-1/#comment-4942</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Fri, 22 Jan 2010 19:52:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.devatwork.nl/?p=594#comment-4942</guid>
		<description>Add another bad/ugly, the community is not really as active as you&#039;d like it to be, I have posted numerous questions that have gone unanswered. I have had better luck googling for my solutions and using question &amp; answer sites like stackoverflow.com.

I consider Liferay an &quot;Open source, closed documentation&quot; project, as most of their &#039;good&#039; information lies inside once you pay for the enterprise edition (my company did).  They make sure not to distribute their documentation even at teaching seminars for fear of having that information released online.  Hence my take on &quot;open source, closed documentation&quot;, the mentality is, you can have it for free, but you figure it out yourself.

The documentation on their website I find to be constantly out-dated, as minor revisions tend to have different methods of doing things. I&#039;ve noticed problems with their wiki too, its not at all up-to-date as one might think.</description>
		<content:encoded><![CDATA[<p>Add another bad/ugly, the community is not really as active as you&#8217;d like it to be, I have posted numerous questions that have gone unanswered. I have had better luck googling for my solutions and using question &amp; answer sites like stackoverflow.com.</p>
<p>I consider Liferay an &#8220;Open source, closed documentation&#8221; project, as most of their &#8216;good&#8217; information lies inside once you pay for the enterprise edition (my company did).  They make sure not to distribute their documentation even at teaching seminars for fear of having that information released online.  Hence my take on &#8220;open source, closed documentation&#8221;, the mentality is, you can have it for free, but you figure it out yourself.</p>
<p>The documentation on their website I find to be constantly out-dated, as minor revisions tend to have different methods of doing things. I&#8217;ve noticed problems with their wiki too, its not at all up-to-date as one might think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franz See</title>
		<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/comment-page-1/#comment-3759</link>
		<dc:creator>Franz See</dc:creator>
		<pubDate>Fri, 06 Nov 2009 10:48:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.devatwork.nl/?p=594#comment-3759</guid>
		<description>Another &#039;ugly&#039; with liferay, is that although it&#039;s open source, it&#039;s a pain to work with its source code.</description>
		<content:encoded><![CDATA[<p>Another &#8216;ugly&#8217; with liferay, is that although it&#8217;s open source, it&#8217;s a pain to work with its source code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Random Links #75 &#124; YASDW - yet another software developer weblog</title>
		<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/comment-page-1/#comment-3748</link>
		<dc:creator>Random Links #75 &#124; YASDW - yet another software developer weblog</dc:creator>
		<pubDate>Thu, 05 Nov 2009 21:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.devatwork.nl/?p=594#comment-3748</guid>
		<description>[...] Liferay: Good, Bad or Ugly? Gute Zusammenfassung. Sehe ich auch so. [...]</description>
		<content:encoded><![CDATA[<p>[...] Liferay: Good, Bad or Ugly? Gute Zusammenfassung. Sehe ich auch so. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nihed</title>
		<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/comment-page-1/#comment-3739</link>
		<dc:creator>nihed</dc:creator>
		<pubDate>Thu, 05 Nov 2009 09:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.devatwork.nl/?p=594#comment-3739</guid>
		<description>Thank you for this article, and I&#039;m totally agree with all points</description>
		<content:encoded><![CDATA[<p>Thank you for this article, and I&#8217;m totally agree with all points</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bert Willems</title>
		<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/comment-page-1/#comment-3727</link>
		<dc:creator>Bert Willems</dc:creator>
		<pubDate>Wed, 04 Nov 2009 17:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.devatwork.nl/?p=594#comment-3727</guid>
		<description>Thank for your input Ashitkin Alexander, I appreciate it. I agree with you it is complex and hard to understand.</description>
		<content:encoded><![CDATA[<p>Thank for your input Ashitkin Alexander, I appreciate it. I agree with you it is complex and hard to understand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashitkin Alexander</title>
		<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/comment-page-1/#comment-3726</link>
		<dc:creator>Ashitkin Alexander</dc:creator>
		<pubDate>Wed, 04 Nov 2009 16:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.devatwork.nl/?p=594#comment-3726</guid>
		<description>For me the ugliest part of Liferay is the build script and it&#039;s output. Why do not single war/ear?</description>
		<content:encoded><![CDATA[<p>For me the ugliest part of Liferay is the build script and it&#8217;s output. Why do not single war/ear?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bert Willems</title>
		<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/comment-page-1/#comment-3709</link>
		<dc:creator>Bert Willems</dc:creator>
		<pubDate>Tue, 03 Nov 2009 07:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.devatwork.nl/?p=594#comment-3709</guid>
		<description>First of all thank you for the compliment. I am sorry to hear that your experience wasn&#039;t as good as mine, have you blogged about it? In that case I would line to link to your post to give people a better insight view on Liferay.</description>
		<content:encoded><![CDATA[<p>First of all thank you for the compliment. I am sorry to hear that your experience wasn&#8217;t as good as mine, have you blogged about it? In that case I would line to link to your post to give people a better insight view on Liferay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neeraj Sidhaye</title>
		<link>http://www.devatwork.nl/2009/11/liferay-good-bad-or-ugly/comment-page-1/#comment-3706</link>
		<dc:creator>Neeraj Sidhaye</dc:creator>
		<pubDate>Tue, 03 Nov 2009 05:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.devatwork.nl/?p=594#comment-3706</guid>
		<description>Nice article, though my experience with Liferay is less but yes this artcile might be a helping reference for me in future...

but yes i also tried working with custom portlet mode ( edit_defaults) and it was not that easy to implement as it is supposed to be....

anyways.. thanks for sharing your experience</description>
		<content:encoded><![CDATA[<p>Nice article, though my experience with Liferay is less but yes this artcile might be a helping reference for me in future&#8230;</p>
<p>but yes i also tried working with custom portlet mode ( edit_defaults) and it was not that easy to implement as it is supposed to be&#8230;.</p>
<p>anyways.. thanks for sharing your experience</p>
]]></content:encoded>
	</item>
</channel>
</rss>
