Portal Pack 3.0 : Makes Portlet Development Easy !!!

Posted: February 13, 2009 in NetBeans

Portal pack 3.0The Portal Pack 3.0 is now available for download. With lots of new features and bug fixes, the Portal Pack 3.0 is out there to make portlet development easier than before. This version is compatible with NetBeans 6.5 IDE. This version of Portal Pack supports the recently released Sun GlassFish Web Space Server 10.0 which is part of the GlassFish Portfolio.
Sun GlassFish Web Space Server is Sun’s next generation aggregation and presentaion platform.  It enables businesses large and small to pull together applications and content from a variety of Web-based and internal sources and present them as a unified, customizable portal on Web browsers, kiosks, and mobile devices. For more info you can check this blog written by James.

Some of the Key Features in Portal Pack 3.0

  • Support for New JSR 286 specification
  • Eventing Storyboard for JSR 286 Eventing
  • Visual Portlet Builder plug-in to build JSF portlet using WYSIWYG editor.
  • Portlets with Spring MVC framework
  • Write Portlets with different languages like Ruby/PHP/Groovy which can be deployed on Sun GlassFish Web Space Server and Liferay Portal Server.
  • Use Web Space/Liferay’s service builder framework inside your portlet. A new advanced Service XML editor is introduced to help you define and generate services.
  • Use Web Space/Liferay’s service apis directly to write advanced portlets.
  • Use Taglibs provided by Web Space/Liferay directly inside your Portlet. For example : You can use rich ui taglibs provided by Liferay/Web Space inside your Portlet, so that your portlet will look similar to other UI in the portal page.
  • Directory deployment : Using new directory deployment feature, you can quickly develop and test your application without redeploying your portlet application again and again. So no need to deploy your portlet when you are changing JSPs, HTML, javascripts etc etc… Also if you are developing portlets using PHP/Ruby/Groovy languages then you need to deploy the portlet only once during development cycle. During development, just change the PHP/Ruby/Groovy script and refesh the browser to see the output.

The deployment support in this release has been extended to support the following servers

Here’s the link to the  quick start guide for Portal Pack 3.0 . So try out this new Portal Pack 3.0  !!!

We have already started working on the next update for Portal Pack. Your feedback for the existing features and suggestions for any new features are most welcome. So you may see your suggested feature in the next update release of Portal Pack.

  1. Angelo D'Angelo says:

    I have some problems with Liferay on Tomcat 6 and Visual JSF Portlet Pages: javascript errors like "invalid characters" and "webui undefined". Do you suggest a workaround?

  2. satya says:

    Are you using Liferay 5.2.1 with Tomcat 6 ? If yes, there was an issue with JSF Portlet on Liferay 5.2.1 . The compressed javascript files are getting compressed again because of some GZFilters which gets injected during portlet application deployment time. But this issue has been fixed in the latest trunk.You can check this LPS for details
    The workaround for this issue in LR 5.2.1 : After deployment of the portlet application, remove all GZipFilter , MinifierFilter from the web.xml of the deployed portlet application. Then restart the tomcat server.
    Let me know if that solve your problem.

  3. Angelo D'Angelo says:

    Thank you Satya. I followed your suggestions and now the portlet does not arise any error. But I have another question: is it possible to use ajax in a jsf portlet (maybe using dyna-faces)?

  4. DJ says:

    Tried PP3 in Liferay 5.2.2 and no components show up. Can’t say that this is compatible with 5.2.x at this point. Unless, someone has a workaround to the problem.

  5. satya says:

    >> Tried PP3 in Liferay 5.2.2 and no components show up.
    What exactly it means ? Are you not able to see the deployed portlets ? Or You are not able to configure Liferay 5.2.2 inside NetBeans IDE.

  6. Angelo D'Angelo says:

    Does Portal Pack 3.0 support Liferay 5.2.2 on jboss-tomcat-4.2.3?

  7. satya says:

    No. It supports Liferay 5.2.2 on tomcat 5.x/6.x and glassfish.

  8. Chris Walters says:

    I am having utter hell trying the develop and deploy a portlet using Netbeans 6.5, Portal Pack 3.0, JBoss 4.2.3, and JBoss Portal 2.7.1. The user interface for this portlet simply displays a few labels and a group of checkboxes where the data for those checkboxes comes from a database. When I build and run the portlet, the labels display fine but the data-bound checkboxes do not show up AT ALL. Any help at all that you can provide would be a great help !! Thanks.

  9. Bob says:

    I am running on RedHat Linux 3.x with Glassfish v2.1, Netbeans 6.5, and Portal Pack 3.0.
    When I try to deploy a portlet from Netbeans I receive the error:
    Massaging could not be done properly. Possible reasons :
    1. Auto deploy directory is not set properly. If so please go to the serverconfig panel and set the auto deploy directory correctly.
    2. Autodeploy scanner might not be responding.
    3. Please restart your sever and try again…
    at org.netbeans.modules.portalpack.servers.websynergy.impl.LiferayTaskHandler._deployOnGF(LiferayTaskHandler.java:157)
    at org.netbeans.modules.portalpack.servers.websynergy.impl.LiferayTaskHandler.deploy(LiferayTaskHandler.java:252)
    at org.netbeans.modules.portalpack.servers.core.PSDeployerImpl.run(PSDeployerImpl.java:151)
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572)
    at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)

  10. Bob says:

    I have glassfish deployed in /opt/glassfish
    My domain is at /opt/glassfish/domains/domain1
    I have my auto deploy set to /opt/glassfish/domains/domain1/autodeploy
    Websynergy is installed at /opt/glassfish/domains/domain1/websynergy and deployed at
    I’m really stumped 😦

  11. satya says:

    Which version of websynergy you are using ? Is it Web Space 10.0 or previous version ?
    Looks like the webspace autodeploy directory (Not glassfish’s auto deploy dir) is not set properly in your case. Just remove the configured server instance from your IDE and reconfigure it again and try.
    Let me know if it works.

  12. Tony says:

    >>Tried PP3 in Liferay 5.2.2 and no components show up. Can’t say that this is compatible with 5.2.x at this point. Unless, someone has a workaround to the problem.
    I get the same problem. After developing a few things on JSF Visual Web and deploying, my portlet comes up blank.
    Using Liferay 5.2.2, Tomcat 6.0 and PP3.0

  13. Sriram says:

    Hi Tony,
    Are you getting any exceptions when you don’t see the components?
    I vaguely remember facing similar issue of not seeing any components ,but after doing a page referesh(or navigating to other pages and returning) the components were getting listed.

  14. Tony says:

    Hi Sriram,
    When I refresh with 5.1.2 the components come up, but not with 5.2.2. With 5.2.2, I’ve tried with Glassfish, Tomcat 5.5, Netbeans 6.5.1, PP 3.01 beta and still nothing comes up.
    And when I add a table with 5.1.2, it will not sort correctly. When I hit the sort button, it goes into idle.
    My setup is:
    Liferay 5.1.2/Liferay 5.2.2
    Tomcat 6
    Netbeans 6.5
    Portal Pack 3.0
    Thanks for the help,

  15. satya says:

    Hi Tony,
    In LR 5.2.2 and later version, you need to add a property "speed-filters-enabled=false" to liferay-plugin-package.properties in your Visual Web Portlet application. Check this issue for more details http://issues.liferay.com/browse/LPS-1998
    Check the liferay-plugin-package.properties for this property. If it’s old portlet project created with portlet with 5.1.x, then this property should not be there. You need to add that manually to make your portlet work on LR 5.2.2 .
    Let me know this solution works !!!
    Thanks !!!

  16. Tony says:

    Hi Satya,
    Thanks for the tip, it still isn’t working correctly. I loaded a static text into the JVWP and it works fine if I click ‘refresh’. And when I click to configure it and click "return to full page" it goes into a infinite load again. And only stops if I click refresh.
    Any clue why that is?

  17. Tony says:

    Hi Satya,
    Actually, I just tested it with IE and it works fine. The problem appears when using Mozilla 3.0.8.
    How can I fix this browser problem with JSF VWP?

  18. Tony says:

    Is it possible to develop a struts portlet with portalpack? any tutorials on how to do that?

  19. satya says:

    Support for Strut portlet is not yet there. But I am sure you can do that by doing some manual stuff. Strut Portlet support is there in our plan, so you may see it very soon in future release.

  20. Tony says:

    cool thanks! When do you think it will be supported?

  21. Tony says:

    Hi Satya,
    I’ve spent so much time trying to fix this, but no luck please help.

  22. Emil says:

    I have the same problem.
    On IE everything is fine. The core problem is between JavaScript code of Woodstock and Firefox. Unfortunately Woodstock is in a "quiet" state and I’m not sure we can expect a fix soon.

  23. Tony says:

    Thanks Emil.
    Netbeans is phasing out the woodstock and migrating to Icefaces. May be icefaces is the way to go now.
    Satya, will you be supporting VWP Icefaces in portal pack in the near future?

  24. satya says:

    Yes, Icefaces should be the way to go as woodstock’s development has been stopped. We also want to see VWP Icefaces support in Portal Pack.
    There’s also a bug filed on Icefaces’s Jira

  25. sriram says:

    Hi Tony,
    Since the JSF navigation sample you attached is working on LR5.1.2 , it appears to me thats a bug in LR 5.2.2..

  26. sriram krishnan says:

    Tony,can you please file a bug for the JSF navigation issue on LR5.2.2 attaching you sample app?

  27. satya says:

    If you are still facing the JSF portlet navigation issue where blank portlet is shown in firefox, then here’s the workaround for it.
    From the jsf jsp page remove webuiAll="true" attribute from <webuijsf:themeLinks……/> tag. Everything works perfectly in Firefox & IE after removing this attribute.
    This issue is still there in Portal Pack 3.0.1 . We will fix it in next update release.

  28. Diego Pietralunga says:

    I’m trying out Portal Pack 3.0.2 on windows with NetBeans 6.7.1.
    I’m stuck with a problem using Liferay5.1.x/5.2.x on TOMCAT 6.0.20 (using Liferay 5.2.x branch from SVN).
    Once deployed Liferay (with some plugins already installed ) in running out of memory,
    "java.lang.OutOfMemoryError: Java heap space" by Spring.
    The problem seems to be the setting of VM parameters to increase memory (-Xmx? ) with cannot be configured by "Services"->"Servers"->"Liferay Portal Server 5.1.x/5.2.x".
    There is NO GUI option for that.
    Can you help, perhaps pointing out a config file for the module for enlarging memory for Tomcat 6.x with Liferay on NetBeans please?
    Thanks a lot.

  29. Pablo Rodriguez says:

    Hi there
    We are trying to deploy on both SunPS 7.1 and WebSpace from netbeans 6.5.1 and portal pack 3.0.2,
    We are not eable to let either of the containers know which are the users.properties file or roles.properties files that we normally specify when deploying from the commnad line or through the web based admin page.
    Is there anyway that we can do deployment from Netbeas (with Portal Pack) specifying these two properties files (for user mapping and role mapping)
    Another question is: is it possible to do remote deplyment to WebSpace using these netbeans plugins.
    Thank you!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s