• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

jsf lifecycle issue

 
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

I have an xhtml page which has

a) <h:selectOneRadio id="NT" onfocus="changeColor(this)"
onblur="changeBack(this)"
valueChangeListener="#{sessMgr.ntLoginChangeListener}"
value="#{sessMgr.windowsAuthentication}" tabindex="1">
<f:selectItem id="item1" itemValue="Yes" itemLabel="Yes"
itemDisabled="false" />
<f:selectItem id="item2" itemValue="No" itemLabel="No" />
<a4j:support event="onclick" ajaxSingle="true"
reRender="userNameLabel,userNameText,passwordLabel,passwordText"></a4j:support>
</h:selectOneRadio>

b) <h:commandButton value="Login"
image="/images/marhaba/submit.jpg" action="#{sessMgr.login}"
tabindex="5" />

both are enclosed in h:form.

Issue is whenever there are two browser instance rendering the same page at same time, neither the valuechangelistener of radio button nor command button working. if i close both browser and access this page in new browser, both of them are working fine.

Any pointer to issue and solution is highly apprecitaed.
 
Saloon Keeper
Posts: 25656
183
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Standard warning: writing your own login processor is a bad idea. J2EE has a much more secure processor built into the J2EE specification which integrates into the J2EE APIs and the appserver.

It would be a lot easier to read your sample definitions if you would https://coderanch.com/how-to/java/UseCodeTags, though.

I'm afraid that I can't tell anything by looking at your samples. They are hard to read, but seem to be basically correct. Although I'm not sure that you realize that the valueChangeListener doesn't fire until the "Login" button is clicked. Listeners do not fire AJAX events. Or any other kind of asynchronous event. In fact, they don't fire events, period - they listen to events.
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic