Hello all,
I am developing a few new portlets for our intranet portal based on Liferay 4.1.2, Tomcat 5.5.20, and MySQL. I am using Sun's Java Studio Creator 2 Update 1 to build JSF JSR-168 portlets, packaged and deployed as .WAR files, deployed using the hot deploy functions in Liferay. Everything works fine, except for the data-bound table components.
The table component is backed up with a CachedRowSet object. This object is bound to the table during the portlet's init() method. In Pluto, this method is called each time the portlet is loaded, like so:
In Pluto, everything works as it should, and the table displays data. Using the pagination functions of the table works properly, as do column sorts and other functions provided by the table component.
In Liferay, the table displays data on the first view, but any subsequent actions, such as a column sort or page forward causes the data to not be displayed.
After googling around for a bit, I found that others have had this issue as well. It stems from the fact that the portlet lifecycle in Liferay is different from Pluto. More info can be found here:
Sun Forum discussion on portlet lifecycle.
Judging by the posts, as well as my own investigation, it appears that Pluto calls the init() method of a portlet page on every render cycle, where Liferay skips it. I can't seem to find a definitive answer about the expected behavior of a JSR-168 portlet with regards to the init() call. The Spec states that init() is for "costly one-time operations" such as establishing DB connections, etc. In this case, wouldn't Pluto be incorrect in calling it during each refresh cycle?
Regardless, I just need to make it work
. Anybody have any suggestions on where to start?
I am developing a few new portlets for our intranet portal based on Liferay 4.1.2, Tomcat 5.5.20, and MySQL. I am using Sun's Java Studio Creator 2 Update 1 to build JSF JSR-168 portlets, packaged and deployed as .WAR files, deployed using the hot deploy functions in Liferay. Everything works fine, except for the data-bound table components.
The table component is backed up with a CachedRowSet object. This object is bound to the table during the portlet's init() method. In Pluto, this method is called each time the portlet is loaded, like so:
dataTable1Model.setCachedRowSet((javax.sql.rowset.CachedRowSet)getValue("#{PSSessionBean.project_stageRowSet}"));In Pluto, everything works as it should, and the table displays data. Using the pagination functions of the table works properly, as do column sorts and other functions provided by the table component.
In Liferay, the table displays data on the first view, but any subsequent actions, such as a column sort or page forward causes the data to not be displayed.
After googling around for a bit, I found that others have had this issue as well. It stems from the fact that the portlet lifecycle in Liferay is different from Pluto. More info can be found here:
Sun Forum discussion on portlet lifecycle.
Judging by the posts, as well as my own investigation, it appears that Pluto calls the init() method of a portlet page on every render cycle, where Liferay skips it. I can't seem to find a definitive answer about the expected behavior of a JSR-168 portlet with regards to the init() call. The Spec states that init() is for "costly one-time operations" such as establishing DB connections, etc. In this case, wouldn't Pluto be incorrect in calling it during each refresh cycle?
Regardless, I just need to make it work
. Anybody have any suggestions on where to start?
Community
Company
Feedback