Added a SystemEventListener to apply the bundle specified by icecore:loadBundle to the view even if the component doesn't get executed, as long as it's in the component tree.
The problem was in icecore:loadBundle and not in ace:dataTable, although it wasn't exactly a bug, because icecore:loadBundle has a different design than f:loadBundle. The difference is that f:loadBundle is a tag handler, while icecore:loadBundle is a component. The advantage of icecore:loadBundle is that it's dynamic, meaning that its attributes can change dynamically, and the changes can be applied on the page dynamically as well, without having to reload the page. However, it gets treated like any other component. This means that it will only load the bundle if it gets executed or rendered in the view. The default behaviour of ace:dataTable ajax events is to only execute and render the table itself. That's why the bundle loaded by icecore:loadBundle wasn't actually loaded in those requests and the messages appeared empty.
This was fixed in a rather unconventional way. When the icecore:loadBundle component object is created, it will subscribe a SystemEventListener to be called after the state has been restored. Then, when this listener is called, the bundle specified by this component instance will be loaded. So, as long as this component is in the component tree, it will load its bundle. After loading the bundle the listener will be removed, to avoid accumulating listeners. Other necessary checks are done before loading the bundle to make sure that it is only applied to the view where the component is declared.
This fix should be tested more thoroughly before the next release, to make sure it works in all situations and doesn't create other bugs.
For now, the workaround is to declare ace:ajax events (for the cases where this problem was seen) and specify the icecore:loadBundle component to be executed in the request.
Bug
Major
Added a SystemEventListener to apply the bundle specified by icecore:loadBundle to the view even if the component doesn't get executed, as long as it's in the component tree.
The problem was in icecore:loadBundle and not in ace:dataTable, although it wasn't exactly a bug, because icecore:loadBundle has a different design than f:loadBundle. The difference is that f:loadBundle is a tag handler, while icecore:loadBundle is a component. The advantage of icecore:loadBundle is that it's dynamic, meaning that its attributes can change dynamically, and the changes can be applied on the page dynamically as well, without having to reload the page. However, it gets treated like any other component. This means that it will only load the bundle if it gets executed or rendered in the view. The default behaviour of ace:dataTable ajax events is to only execute and render the table itself. That's why the bundle loaded by icecore:loadBundle wasn't actually loaded in those requests and the messages appeared empty.
This was fixed in a rather unconventional way. When the icecore:loadBundle component object is created, it will subscribe a SystemEventListener to be called after the state has been restored. Then, when this listener is called, the bundle specified by this component instance will be loaded. So, as long as this component is in the component tree, it will load its bundle. After loading the bundle the listener will be removed, to avoid accumulating listeners. Other necessary checks are done before loading the bundle to make sure that it is only applied to the view where the component is declared.
This fix should be tested more thoroughly before the next release, to make sure it works in all situations and doesn't create other bugs.
For now, the workaround is to declare ace:ajax events (for the cases where this problem was seen) and specify the icecore:loadBundle component to be executed in the request.