Trinidad + Richfaces = Problem (solution)

Finally after 3 days of googling and a trial-and-error approach I've found out how to overcome the problem with links in a table being stripped from javascript code after an Ajax call (for example for pagination or sorting columns).

The answer to that is a4j:htmlCommandLink (instead of h:commandLink) inside an a4j:form (instead of h:form). Don't ask me why - it's to complex to describe the actual bits and pieces behind some sick concepts in those libraries. The final fact is that h:commandLink ain't working but the a4j:htmlCommandLink is. Period.

Later today I'll attach a working project with the solution. For now you're just going to have to trust me on that one :D

RichFaces 3.3.1 Bug

Another day got lost because of some guy trying to make things that work better. This time it's sorting of columns generated from list. All used to work until version 3.3.0.CR1 and then, all of the sudden, it stopped. You can click the damn header all you want and nothing happens.

Components involved: rich:dataTable and rich:columns

O my gosh how I hate those days...

RichFaces + Trinidad = problems

I've been fighting for over 3 days on that so you might wanna listen to the story not to make the same mistake I did.

Some time ago someone decided to use JSF libraries in our project. That same someone decided to use RichFaces (a nice library indeed) and Trinidad (the most terrible piece of code I've ever encountered) in one project.
As the story continued we've been using both of those libraries and it worked quite nice right up to the point where I wanted to use rich:datascroller on a rich:dataTable component containing some action links.

Just so that you know what I'm talking about I'm giving you 2 small projects that show the problem. One without Trinidad configuration (this one is working just fine) and the other one with Trinidad.

example-01-working.zip
example-01-not_working.zip

Basically the Ajax rendering engine from RichFaces is being crushed down with the one from Trinidad. They just hate eachother!

I've never ever expected that 2 libraries might have such a negative impact on eachother! What a waste of time!!!