Liferay 4.4.0 open-source portal released


News: Liferay 4.4.0 open-source portal released

  1. Liferay 4.4.0 open-source portal released (17 messages)

    Liferay 4.4.0 has been released. Liferay is an open source portal in wide use, and this release offers many new features on top of the already-robust feature set, such as an improved user system, better content management, developer improvements, and usability improvements. Bundled with multiple application servers (Geronimo, Glassfish, JBoss, Jetty, Tomcat, Resin, JOnAS, and Pramati), Liferay follows the normal installation procedure for the application server chosen. For example, the Glassfish bundle ran the normal Glassfish installer (without the normal memory setting requirements, oddly enough) and simply included the Liferay application as part of the installation. The installation was entirely normal, even requiring Glassfish' normal "ant -f setup.xml" after basic installation. It's hard to get much simpler than using the normal installation procedure of the bundled application server. The application takes a while to start up, but that's not unusual for portals; once initialization is done, you have a copy of the liferay portal from (This is part of the default embedded database, and isn't meant for production use. As mentioned later, switching to another datasource installs a different theme.) Logging in with test at liferay dot com/test, one finds the display a little spartan - but going to add applications under the user menu shows you where Liferay shines. You can drag and drop one of the provided portlets to a desired location on the current page, and voila! You now have a displayed portlet. The provided portlet set is quite large, ranging from journal entries (which, in fact, make up the normal display) to a wiki, to a calendar, message boards, polls, weather display, page rankings, all kinds of things. Liferay was really horribly slow on first installation. That's because it's using the default HSQL database, which is great for development but gets absolutely hammered by Liferay. (It should be noted that the installation documentation for Liferay tells you that HSQL isn't the right long-term choice for a portal.) Switching to a JavaDB (i.e., Apache Derby) database connection pool sped things up dramatically - and also provided a new portal configuration to work with, which is actually a little nicer to play around with than the site template. It's very nice to work with, once you switch away from HSQL - the portal is far more responsive and the default template is quite nice - and the administration page allows you to install themes that range from desktop-like to a zen theme. The supplied portlets are very useful as well, even including a WSRP portlet for remote hosting of portlet content. One thing should be noted, though: the portal is very verbose. Watching the server logs under Glassfish, Liferay shows warning after warning, and information line after information line. While some of the information is likely to be very useful, after a while, the messages lose meaning; there are simply too many of them to be useful, by default. It's easy to turn them off, by changing the log level for to something other than WARN (other application servers will have their own configurations!) but it's still annoying - and using System.out for such messages makes configuration a bit of an all-or-nothing affair. Liferay has done an excellent job with this release; it's cleanly installed, very easy to use, and quite full-featured. While a quick run-through simply can't show off every feature a portal offers - for example, no custom portlets were written and deployed - the capabilities displayed should fit most organizations' needs immediately, outside of specific custom portlet requirements. The WSRP portlet should make even custom portlets easy to work with. Altogether, this is an excellent update.

    Threaded Messages (17)

  2. Good news for the community[ Go to top ]

    Liferay is the best portal in the world. Congratulations to the Liferay team for this new exciting release!
  3. Liferay is just a toy[ Go to top ]

    Liferay is not that great,I had performance issues using Liferay on Tomcat with https. I've enabled HTTPS and KABOUM!, the performance was so slow I had to hack the Liferay code to merge web resources(.js, .css, ...). There's just too much files and resources per request. Resources are not cached with HTTPS (except maybe on the Firefox browser, if you enable secured cache) Liferay ... you're cute but waaaaaayyyy too fat.
  4. Re: Liferay is just a toy[ Go to top ]

    That's actually an HTTPS issue and has nothing to do with Liferay itself. We solve this for large client sites by using HTTPS servers that do the hard math work for us. By default, we don't pack or aggregate any of the JS or CSS, so you end up with a lot of files that the HTTPS server has to go through. By setting these properties in Your YSlow! score will go from an F to an A (add a CDN and other stuff) We're running in many many large enterprises with hundreds of thousands of users to millions of users for many years already. We've been the front end aggregator / portal for large banking institutions and military instituations who consider us central to their web presence. With that said though, our community at is very active and we'd love to address more of your concerns so that we can improve our product to better fit your needs. Thanks Jean.
  5. Performance[ Go to top ]

    What is the little light green circle rounding in each portlet in ur DEMO page ????. I am little scared to even add another page and fire a page rendering. It might a good look and feel and even have bunch freebeeze client, but still have to address the enterprise portal concepts. SO Make ur DEMO as default 25 pages portal application and run that in a simple tomcat server with 2 cpu hardware and make sure all that greem circles go away from user's html page without asking them to take coffee break to see the rendered page( Anyway it is not that much big deal in 21st century computing, but show it)
  6. liferay in action[ Go to top ]

    Is anybody using liferay here. Please post your site. thanks
  7. Re: liferay in action[ Go to top ]

    Is anybody using liferay here. Please post your site.

    Can't. Internal.
  8. Re: liferay in action[ Go to top ] - but it's all private, sorry. We've used Liferay for over 3 years and it's been great.
  9. Re: liferay in action[ Go to top ]

    Is anybody using liferay here. Please post your site.

    Spring uses it to power their site:
  10. Re: liferay in action[ Go to top ]

    This page links to deployments of Liferay not protected by a NDA.
  11. Re: liferay in action[ Go to top ]

    Is anybody using liferay here. Please post your site.

  12. Re: liferay in action[ Go to top ]

    This should bring up a handful of public sites: google search Message was edited by:
  13. Re: liferay in action[ Go to top ] uses Liferay 4 (but not 4.4 yet!) Nicolai
  14. Re: liferay in action[ Go to top ]
  15. Re: liferay in action[ Go to top ]

    Is anybody using liferay here. Please post your site.

    thanks We use liferay as frontend for our articles which are held in an CMS.
  16. Production Sites[ Go to top ]

    WhereToGo at - in production Click Magazine at - will move this week (including excellent SEO) Some people believe that performance is a problem... 99% wrong. Yes, it is an obvious problem with Mozilla for logged in users (somehow Mozilla sucks with AJAX so that Google has stopped advertising it and started promoting Chrome). Performance is not a problem for external users. Too fat... yes, with a lot of bugs. I fixed yesterday "toLowerCase()" bug with VirtualHostFilter... am I first user who sees such problem with Friendly URLs?!! Database Indexes: extremely weird!!! MySQL: works with MyISAM only (non-transactional!!!) - heavy "SELECT COUNT(*)" usage. This is site to compare with: Shopping Engine - much faster, thanks to Spring MVS and Lucene.
  17. Production Sites[ Go to top ]

  18. Liferay Performance is Excellent!!![ Go to top ]

    Click Magazine at - just a sample of recent addition. Thanks to Liferay! 3-months, 2-developers, fast development time for such rich functionality (including SOA integration with partner sites: they publish our articles, weekly polls, horoscopes, and etc.) Most of initial complains about Liferay performance are related to logged-in user experience in development environment; use and in your to see the difference, and use Apache HTTPD with mem_cache enabled. Too often bad performance relates to logged-in sessions with Mozilla Firefox and AJAX. Some (and only some!) portlets had bad client-side performance in Liferay v.4.x (for instance, "manage pages" portlet with IE, or "Journal VM Template" with Firefox) which were fixed in Liferay 5.1. And 'client-side' or 'custom-portlet-specific' performance should not be considered Liferay-specific. Click Magazine at Check our site with Firefox + Live HttpHeaders plugin: - gzipped output (20kb) - proper 304 (not modified) HTTP headers for almost everything. Oh, we forgot to mention: Liferay supports integration with CDN such as Akamai. Regards, Tokenizer Inc.