As you can see, when clicking the button "Continue", the amount (wich is a h:inputText with a valueChangeListener and a 'a4j:ajax event="change" render="xxx" ') has been updated using a converter to display it properly and then the action linked to the a4j:commandLink is fired rendering the content below.

I have made an update version of RichFaces. I am now using RichFaces 4.3.2.Final with JSF 2.1.19 and the behaviour of my a4j:commandLink has changed:

Step 1:

Step2 (after clicking the button "Continue" wich is a a4j:commandLink):

Step 3 (after clicking the button "Continue" once again):

The first click on the a4j:commandLink does not fire the action behind it, instead the change event is applied on the amount and user has to click again on the button to have it work. Is there anyway to have the same behaviour than before because it causes the user to click twice?

Can you provide the facelet source behind the above examples? Your use case *should* continue to work. eirther there is an error in the code, or a bug in either RichFaces or Mojarra (or are you using MyFaces?).

You can also try upgrading just one jar at a time. Use RichFaces 4.3.2.Final with Mojarra 2.1.8 and/or RichFaces 4.2.3.Final with Mojarra 2.1.19. This would help narrow down whether the problem lies in RichFaces or in Mojarra.

I'll try to do it as soon as possible. I have also encountered issues with IE8 and IE7. It looks like the packed.js crashes with those browsers (it works well with FF and Chrome), have you got any idea that could help?

On re-reading the issue I just noticed that you mentioned you use portlets. Do these errors you are describing only manifest themselves in the portlet environment? If you put the same code in a "vanilla JSF + RichFaces" application does it work correctly? Knowing this will be important in narrowing down the source of the problem.