This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 94752 - selection components: immediate property does not work
Summary: selection components: immediate property does not work
Status: RESOLVED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: Matthew Bohm
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-06 20:22 UTC by bugbridge
Modified: 2007-06-27 03:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-06 20:22:04 UTC
Original status: 3-Accepted; Suggested Status: NEW


Original submitter: syz

Description:
qBuild 1b

1. Add a dropdown or other selection component, such as checkbox group, listbox.
2. Set its immediate to true. 
3. Set its auto-submit on change
4. Add a textfield, set it to required.
6. Add a message group
5. Run

Select an item from dropdown. Expect it won't show any error. It actually shows
value is requried message. 

It happens in Thresher and Leopard too.

Evaluation:
I should check the original SignOn sample app to determine what functionality
was supported when combining auto submit on change with immediate. Of course, I
advocate virtual forms, so downgrading to P4 and marking accepted.
Comment 1 Matthew Bohm 2007-06-27 03:06:06 UTC
If you put renderResponse() at the end of your processValueChange method for the dropdown, it should work. Try it. I
confirmed this is what is done in code sample 10 of
http://developers.sun.com/jscreator/reference/techart/2004q2/signon_app.html. Calling renderResponse() will essentially
short-circuit the lifecycle, bypassing the normal validation phase (in which the non-immediate components will otherwise
be validated).