The major components, datatable, extendeddatatable etc.. really disapointing. Rendering and other errors easy to find.
just words. but need real issues reports to check and confirm.
The live demo can't be based on the official release.
but it's based.
maybe just too much magic in the app code? ;)
I have to agree with Ilya. I've not found many weird things with the 3.3.1 release with datatables and rendering. The only thing is that when I use a datascroller or select something in a datatable, *all* other datatables in the same page get some kind of signal to access the model (but do not do anything with it, so it is no performance issue)
yes.. dataTables gets model automatically at encode because need to check the columns for auto updatable components presence (outputPanels, messages and so on) But it's could be resolved since 3.3.2 using limittolist=true at action component. The components specified in the reRender only will be updated in this case.
since 3.3.0 sorry
Maybe it's based, maybe the wrong words.
But the version used for the live demo is definitely not the official release, I copy'n pasted the examples into a 3.3.1 project and there are a lot of bugs easy to find.
Example with extendedDatatable :
drag the colums in Firefox -> doesn't work in a professionell way.
dragging the columns to optimistically in IE -> leeds to an exception
using grouping of columns in IE -> leeds to a crippled text output
Don't know how all this could make it into the release.
The differences between the demo and your application could be caused by many reasons and environmental details.. But the demo deployed with release jars for sure and will works the same if you will download and run it locally. Could you please share somewhere your sample war file for investigation?
Hi lgsuperboss, I'm also working with the current RF-release and a lot of datatables and haven't found big stopping issues for my kind of usage.
I'm sure that you know, that not always the framework must be the source of the problem, and I'm also sure, that you know the way of asking for help (or whatever you want? don't know how to interpret your posts?) is a leading way how to help you.
By the way:
Nothing will constraint you to skip in some JIRA's, with detailed error description and reproducable way to find them.
Also nothing will hinder you to change the underlying JSF-Componentframework.....if you think, you can handle another framework in a better and easier way - just do it. 8-}
PS: Bugs are a normal part of SW-development.....otherwise we would be jobless....;-}
I'll post a new topic on the issue of accessing the datamodel. SInce I use 3.3.1.GA and limitToList=true etc, I'm curious then if I still do something wrong. First trying 3.3.2-SNAPSHOT and see if that makes a difference (although you mentioned 3.3.0 as a correction ;-))