Ling Lin

Greenhorn
+ Follow
since Aug 08, 2012
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Ling Lin

Hi everyone,

I'm having a problem with the selectOneRadio component in JSF1.2 where if user clicks on the label of the radio button, old selection value would still be passed as parameter in the ajax call. However if I click on the actual radio button of the option, everything works fine. New selection value will be passed.
====================================
[] Option 1 [] Option 2 [] Option 3

Steps:
Page starts with option 1 selected by default
Case 1:
If I click on the text "Option 2", JSFUtils.getParameters("paymentOption") will still return 0, which is the value of "Option 1"
If I then click on the text "Option 3", JSFUtils.getParameters("paymentOption") will return 1, which is the value of "Option 2"
Case 2:
If I click on the radio button "Option 2", JSFUtils.getParameters("paymentOption") will return 1, which is the correct value of "Option 2"
If I then click on the radio button "Option 3", JSFUtils.getParameters("paymentOption") will return 2, which is the correct value of "Option 3"
=====================================

Could someone please help me figure out how to fix this? Can I make clicking on label to have exact same behaviour as clicking on radio buttons?

Any help is greatly appreciated!

Code:





11 years ago
JSF
Thank you all who came in and help

I'm trying to solve this JSF related issue but I'm totally new to JSF. I did quite a bit search but I'm still clueless...

Environment:
Websphere 7
JSF 1.2
JSF (IBM Compatibility) 7.0
JSF (IBM Enhanced) 7.0

Client is seeing a lot of the following exceptions in their production server log since we upgraded to WAS7 and JSF1.2 but we haven't been able to reproduce this in dev or testing (probably because the volumn is much smaller). Everything worked perfectly fine in testing and production before the upgrade:




ErrorModelBean.java:


Could anyone provide a little thoughts?

Any help is appreciated! THANK YOU!
11 years ago
JSF