You omitted the el-api/impl-1.0.jars. This breaks the
i ve some problems in Richfaces Tree, i ve posted my problem in this forum but still am not able to get any clue how to do..
this is my thread.. can u please tell me how to do..
Guys, sorry but read carefully the Sergey's comment in 3133 bug. This issue needs to move critical changes to branch in order to be fixed in 3.1.6. We can not do this.
So basically what you are saying is that it is against your policy to fix a bug because too much changes would be required.
I see - that leaves the "stable" 3.1.x branch with a mess of a buggy component (that is scrollableDataTable).
What I think most of the users meant by top priority stability is that you don't add NEW features before really getting the old components to a level that can be considered stable (= no critical bugs).
3.1.6 will continue in my book of failed RF releases.
You should be considering ditching the scrollableDataTable in 3.1.x all together if you don't plan to fix its problems.
Sorry for my harsh words but that just really upsets me.
You could better understand us if you try to look to the jira and look through the scrollableTable bugs on 3.2.x branch(many of them doesn't pressent in 3.1.x).
We can't just move new bugs to the branch in order to get one bug fixed.
This newes bugs caused by our review old template and some code and rewriting some blocks. So the code changed too much and could be more harmfull for the users that uses the scrollable from 3.1.x right now.