I'm upgrading an application from RichFaces 3.3.1 to RichFaces 4 and it's been a very frustrating experience. It's very poorly documented compared with RichFaces 3.3.x so that's making it harder. They've added some controls, but taken away others. In the ones they've kept, they've changed some attributes either in name or functionality, and in cases neglected to document these changes.
The thing that's killing me though is the rich:extendedDataTable, which is a control we were using extensively. The "upgrade" seems to have removed large amounts of functionality like column grouping and made things like sorting much harder to implement. I can't tell if I'm just not finding the right path through the meager documentation, or if the Richfaces 4 team has really messed this up. I may have to eat crow and convince my company to back off this upgrade. That's going to tough since I was the primary proponent of it.
Hi Greg, the best I can suggest is to take a look at what's going into 4.1, it's scheduled for 22-Nov and they're
taking votes (from the richfaces jira) for what's going into the milestone 3 release. No doubt it'll be a bit of a
pain to have to trawl through the issues finding which existing ones correspond to your own problems, but the
more votes, the more chance of getting things fixed. I'm taking a hit right now without pickList & contextMenu,
pickList having been confirmed for 4.1. I had problems with popupMenu but this was something that I was
very easily able to just transition to a jQuery only solution, and it works great. I've written an autocomplete
custom component because the existing 4.0 solution doesn't have pojo support (i.e. you can just deal with
strings rather than more complex objects, the rich:column support doesn't work). I couldn't get inplaceSelect
working either so there are a good few issues I'm hoping to see fixed in 4.1.
A strategy I'd like to develop is using jQuery plugins for the client side solution with a4j:jsFunction for
communication with the server. I'm just looking at what would need to be done to put a pickList solution
together with jQuery. I expect this will lead to messier code but as long as it works, and remains working I
Thanks Brendan, that's by far the most helpful answer I've received anywhere on RF4 questions. We don't have a jQuery expert on our team, so we're talking about dropping down to RF 3.3.3 and keep an eye on RichFaces 4 to see if they re-implement some of the things they lost. I'm a bit upset with the RichFaces team though. I know it's open source and free, but they still could have been much more complete in documenting what functionality had not made it into the "final" release. That would have saved me some time ... and hair!
Joined: May 12, 2009
I understand your concerns. Don't blame yourself too much, the problems that you are
experiencing are widely felt. The thing that kills me is a loss of contunuity, I can leave
the righteous path of progress to work around a bug, and the next thing I know it's
eight weeks later and I've not really moved ahead.
Brendan, I share the frustration with how RF4 is poorly documented and how we have lost functionality (so it seems) with some of the components. You mention autocomplete here (which I am also struggling with) and perhaps a workaround? Here is what I have working in RF3 with suggestionBox:
I cannot figure out how to fire the function "managePreferredListBean.retrieveMasterParty(result)" when a choice is made from the suggestions nor can I figure out how to increase the width of the autocomplete box (width=400 isn't working).