[fvsiss]

I was having the same problem and luckily found this thread. Both options separately applied seem to fix the problem.

1) Switching to an older version of ajax4jsf (I believe 1.06)

or

2) Upgrading the JSF 1.1_01 to JSF 1.1_02

However, Option #2 seems to break much of our existing web application. So I'm curious, is this issue being looked at for a future build in ajax4jsf? Since ajax4jsf says it works with JSF 1.1, I would think this needs to be addressed. Or does that statement mean ajax4jsf will only work with the latest version of JSF 1.1?

Thanks in advanced, for any replies

[ilya_shaikovsky]

This is one of the JSF bugs not the ajax4JSF-one. And there are more another in JSF 1.1_01. So you need to upgrade.

2) ajax4jsf latest version is 1.2 available from Snapshots.

[emil.olofsson]

Hi all,

I'm also having this kind of problem. But I'm using JSF 1.2 and not 1.1 as you are discussing in this thread.

I have tried with different versions (1.1.1, 1.1.0 and 1.0.7) of ajax4jsf but it doesn't solve my problems. I'm using JBoss 4.0.5 GA and Richfaces 3.0.0.

Any suggestions?

Best regards,
Emil

[ilya_shaikovsky]

Please attach me the war file to reproduce.

http://jira.jboss.com/jira/browse/AJSF-97

Thanks.

B.t.w. Rich Faces 3.0.0 is too old. Use please 3.0.1 release in future.

[alexndr]

Hi guys.

Any progress on this one?

BR
Alex