Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.1
-
Fix Version/s: 3.2
-
Component/s: Sample Apps
-
Labels:None
-
Environment:ICEFaces + WebSphere Portal
-
Affects:Compatibility/Configuration
Description
The Ajax update code associated with the data table selection code doesn't appear to update the server. The problem is visible in Ace data table listener and Ace data table row selector demo pages. The page has an area which is supposed to reflect what has been recently selected. The examples don't show any updates whatever at the moment.
In the row selector example, Console shows the following message on selection event:
[23/08/12 10:16:56:092 PDT] 00000033 ComponentUtil I Cannot find component with identifier "selectForm:status" in view.
In the data table listener example, console shows the following message on selection event:
[23/08/12 10:18:04:834 PDT] 0000003e ComponentUtil I Cannot find component with identifier "listenerForm:eventLog" in view.
In the row selector example, Console shows the following message on selection event:
[23/08/12 10:16:56:092 PDT] 00000033 ComponentUtil I Cannot find component with identifier "selectForm:status" in view.
In the data table listener example, console shows the following message on selection event:
[23/08/12 10:18:04:834 PDT] 0000003e ComponentUtil I Cannot find component with identifier "listenerForm:eventLog" in view.
I ran the trunk against Liferay and see the same thing. Looks to be a problem with rendering out the JavaScript behaviours for the ice.ace.Datatable (formatted slightly for readability):
behaviors:{select:{
source:"A7601:listenerForm:carTableSingleRow",
execute:"A7601:listenerForm:carTableSingleRow listenerForm:eventLog",
render:"A7601:listenerForm:carTableSingleRow listenerForm:eventLog",
event:"select"}}
You can see that the source id has the portlet namespace (A7601) and the first render/execute id has the namespace but the second render/execute id does not have the namespace. This causes the problem of not being able to find it. It's not quickly clear to me where this all gets handled in the rendering code so we may need to assign the JIRA to somebody in the component team.