• 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:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

actionListener a crap shoot

 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This is a general kind of question. When I stick an actionListener on a commandLink, it seems to be a crapshoot whether the method defined in the actionListener attribute is actually called or not.

Lately I've had problems where they work in Firefox but not in IE. But that's not my specific question.

I have code that works that I copied to a new view and suddenly it doesn't work.

Sometimes the problem is that the component is not enclosed in a form.

Once I put a phaseListener on my app and when I clicked on the commandLink the phaseListener showed a jump straight to phase 6 even though I had input fields with text in them. The text never seemed to get submitted.

Can someone explain some situations where this might occur? Why? Or point me to a reference that explains this better? I've read over and over about the JSF Lifecycle. It makes some sense but I still don't really grasp what happens here.

Thanks,
Tanya
 
reply
    Bookmark Topic Watch Topic
  • New Topic