Hi all,
First of all, congrats for the new Ajax features
a:outputPanel is simply wonderful
i have a not normal behaviour :
i have a Seam application ( In production with 1.2PATCH )
and it is working well on Jboss 4.0.5GA
I put an apache in front of jboss with ModJK.
SO is Fedora RC6.
if i use
http://xxxxxxx:8080/xxxxxx
it is all right
if i use
http://xxxxxxx:80/xxxxxx on the same page
and i push my
a:commandLink
i have to push it 1 or 2 or 3 or 4 times to make the application working
yes, i am not dreaming, i have to push it many times, like an old juke box :-)
Perhaps it is not the right forum to post this issue.
Any case
Good work with Seam, it is n. 1 :-)
and sorry form my bad English
Nicola
Architect - Developer
X-GATE Milano
If it's working fine when you access the AS directly, not through a proxy, then the problem is unlikely to be Seam related, but due to your proxy setup. Perhaps try asking on the JBoss Ajax4jsf users forum as someone might know more there.