BUG: jspx editor complains about missing method from superclass of bck bean

Question

Hello,
I have found a bug that is more an annoyance than anything, but wanted to report the behavior. Here is the scenario:
1). Create a bean (I'll call it the super_backing_bean)
2). Put an action listener in the bean (I'll call it al)
3). Create a JSPX page
4). Create a backing bean for the jspx page (I'll call it page_backing_bean). Make page_backing_bean extend super_backing_bean.
5). Put a command button on the page. Bind it's actionlistener to #{page_backing_bean.al}. The pop-up properties editor allows you to do this nicely.
6). Open the jspx page in "source" view and look for the command button. There's a red squiggly under the actionListener property. If you hover over it, you get "The method al does not exist in the bean page_backing_bean"
Note this is merely an IDE bug. The code works as expected during run time.
Kind regards,
John

Answer 1

Hi Harry (and others),
I have seen similar behavior. It seems like the client side rendering for some reason has a hard time processing the collection model wrapping the ArrayList in this particular case. The table renders empty. After sorting in ascending order, the rows are all back (visible) again.
Is anyone aware of issues with the rich table based directly on ArrayList (in combination with a changing set of values and/or sorting)? (seems like a corner case but is still not uncommon). Is there any indication that wrapping the ArrayList in a CollectionModel ourselves might be required?
Harry: do you know whether this issue is introduced with PS3 (11.1.1.4) or already existed in previous releases?
kind regards,
Lucas