Hi, As some of you may have seen, I pushed the current Portlet Hub Ajax prototype to the Pluto GIT repository. The prototype contains the following functionality:
* Initial page state is set up based on the current state as available on the server. * Portlet Client registration * Add / remove listeners for the onStateChange and onError system events * Portlet Client is notified of its initial state after an onStateChange listener is added * Portlet Client is notified when the portlet state changes * Portlet Client is notified when a public render parameter that it uses is changed * The setPortletState method can be used to set public & provate render parameters * A resource URL containing the page state along with resource parameters can be generated. * For a resource URL, the cacheability settings FULL, PORTLET, and PAGE are respected and state on the URL is adjusted accordingly As currently written, the Portlet Hub is available on every portal page. Sometime it might be good to move the PH initialization code from default theme into a JSP tag, but that currently isn't high on my list of priorities. The prototype also contains portlets that demonstrate this functionality. I added the portlets as a separate module to the Pluto build. We might not want to leave them there forever, but I think it's convenient to have them there for now. However, the portlets are not deployed automatically. If you want to try it out yourself, you can do the following: * Clone the repo from: https://git-wip-us.apache.org/repos/asf/portals-pluto.git * Checkout the "PortletHub" branch * Build Pluto using: mvn clean install * Deploy to Tomcat using: mvn pluto2:install -DinstallDir= .... path to your tomcat ... * Copy the demo portlet WAR file from PortletHubDemo/target to the Tomcat webapps directory * Edit the Pluto page config file to add an appropriate page with the demo portlets Have fun! I am currently working on extending the prototype to add the Ajax action functionality. That will complete the PH functionality for non-JSF portlets. I'm actually pretty far along, and hope to be able to demo that functionality during our next EG call on this coming Tuesday. When that is finished, I'll implement the Partial Action support, completing the envisioned Portlet Hub API, and enabling a JSF Portlet Bridge to use the Portlet Hub. Mit freundlichen Grüßen, / Kind regards, Scott Nicklous WebSphere Portal Standardization Lead & Technology Consultant Specification Lead, JSR 362 Portlet Specification 3.0 IBM Software Group, Application Integration Middleware IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
