ICEfaces
  1. ICEfaces
  2. ICE-6156

Portletize the Advanced Component Showcase

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-Beta1
    • Fix Version/s: 2.0.0
    • Component/s: ACE-Components, Sample Apps
    • Labels:
      None
    • Environment:
      ICEfaces 2 ACE portlet
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial

      Description

      Need to provide the portlet artifacts and build targets for portletizing the Advanced Component showcase examples.

        Issue Links

          Activity

          Hide
          Deryk Sinotte added a comment -

          Due to the conflicts between the version of YUI we currently load and use in ICEfaces 2 and the version that is loaded and used by Liferay, that issue needs to be resolved first.

          Show
          Deryk Sinotte added a comment - Due to the conflicts between the version of YUI we currently load and use in ICEfaces 2 and the version that is loaded and used by Liferay, that issue needs to be resolved first.
          Hide
          Deryk Sinotte added a comment -

          ACE Showcase Portlet Testing

          Liferay 6.0.5

          It's possible to load a single ICEfaces portlet in the page and basic functionality appears to be there. However, there are two major issues:

          1) Still appears to be a YUI conflict even when both Liferay and ICEfaces are both using the same version (3.2). Likely still due to the extra evaluation of YUI code which appears to still cause an issue. The problem now is that, since ICEfaces loads last, it's causing some re-evaluation of scripts that Liferay is dependent on for it's UI. The end result is that, after the first ICEfaces ACE portlet has been added to the page, you can no longer move it around or add any other portlets to the page because the Liferay UI no longer functions correctly. I'm seeing the following JS issues several times in the console:

          Uncaught TypeError: Cannot read property 'event' of undefined
          m.use.H everything.jsp:1
          v.each.w everything.jsp:1
          m.use.H everything.jsp:1
          m.use everything.jsp:1
          (anonymous function) ace:53

          2) There seems to be some issues around loading CSS properly. I see these types of things in the Chrome console regarding the resources where the URLs to be imported are not properly resolving to what the portlet requires.

          /* load core styling from YUI library */
          @import url('http://localhost:8080/web/guest/ace?p_p_cacheability=cacheLevelPage&p_p_col_count=1&p_p_col_id=column-1&p_p_id=checkbox_WAR_aceshowcaseportlet_INSTANCE_PG9o&p_p_lifecycle=2&p_p_mode=view&p_p_state=normal');
          @import url('http://localhost:8080/web/guest/ace?p_p_cacheability=cacheLevelPage&p_p_col_count=1&p_p_col_id=column-1&p_p_id=checkbox_WAR_aceshowcaseportlet_INSTANCE_PG9o&p_p_lifecycle=2&p_p_mode=view&p_p_state=normal');

          Liferay 5.2.3

          No JS conflict here but there are other problems.

          1) The first interation with any portlet causes the following:

          Caused by: java.lang.ClassCastException: com.sun.faces.application.view.StateHolderSaver cannot be cast to [Ljava.lang.Object;
          at javax.faces.component.UIOutput.restoreState(UIOutput.java:251)
          at com.sun.faces.application.view.StateManagementStrategyImpl$1.visit(StateManagementStrategyImpl.java:261)
          ... 121 more

          2) The same CSS resource loading/importing issues as described above for Liferay 6.

          Show
          Deryk Sinotte added a comment - ACE Showcase Portlet Testing Liferay 6.0.5 It's possible to load a single ICEfaces portlet in the page and basic functionality appears to be there. However, there are two major issues: 1) Still appears to be a YUI conflict even when both Liferay and ICEfaces are both using the same version (3.2). Likely still due to the extra evaluation of YUI code which appears to still cause an issue. The problem now is that, since ICEfaces loads last, it's causing some re-evaluation of scripts that Liferay is dependent on for it's UI. The end result is that, after the first ICEfaces ACE portlet has been added to the page, you can no longer move it around or add any other portlets to the page because the Liferay UI no longer functions correctly. I'm seeing the following JS issues several times in the console: Uncaught TypeError: Cannot read property 'event' of undefined m.use.H everything.jsp:1 v.each.w everything.jsp:1 m.use.H everything.jsp:1 m.use everything.jsp:1 (anonymous function) ace:53 2) There seems to be some issues around loading CSS properly. I see these types of things in the Chrome console regarding the resources where the URLs to be imported are not properly resolving to what the portlet requires. /* load core styling from YUI library */ @import url('http://localhost:8080/web/guest/ace?p_p_cacheability=cacheLevelPage&p_p_col_count=1&p_p_col_id=column-1&p_p_id=checkbox_WAR_aceshowcaseportlet_INSTANCE_PG9o&p_p_lifecycle=2&p_p_mode=view&p_p_state=normal'); @import url('http://localhost:8080/web/guest/ace?p_p_cacheability=cacheLevelPage&p_p_col_count=1&p_p_col_id=column-1&p_p_id=checkbox_WAR_aceshowcaseportlet_INSTANCE_PG9o&p_p_lifecycle=2&p_p_mode=view&p_p_state=normal'); Liferay 5.2.3 No JS conflict here but there are other problems. 1) The first interation with any portlet causes the following: Caused by: java.lang.ClassCastException: com.sun.faces.application.view.StateHolderSaver cannot be cast to [Ljava.lang.Object; at javax.faces.component.UIOutput.restoreState(UIOutput.java:251) at com.sun.faces.application.view.StateManagementStrategyImpl$1.visit(StateManagementStrategyImpl.java:261) ... 121 more 2) The same CSS resource loading/importing issues as described above for Liferay 6.
          Hide
          Deryk Sinotte added a comment -

          The ACE Showcase example has files and build target for creating a portlet version. Due to ICE-6164, only the File Entry component currently works as a portlet at the time being. Future work to re-able the other portlets are dependent on work in ICE-6164.

          Show
          Deryk Sinotte added a comment - The ACE Showcase example has files and build target for creating a portlet version. Due to ICE-6164 , only the File Entry component currently works as a portlet at the time being. Future work to re-able the other portlets are dependent on work in ICE-6164 .

            People

            • Assignee:
              Deryk Sinotte
              Reporter:
              Deryk Sinotte
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: