
| Key: |
WW-1489
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Konstantin Pribluda
|
| Votes: |
1
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
WebWork
Created: 30/Nov/07 02:26 AM
Updated: 02/Dec/07 09:35 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
2.2.6
|
| Fix Version/s: |
2.2.7
|
|
|
It is known, that browser do not send anything for unchecked checkoxes -
thus webwork in current state can not actively set "false" value to boolean fields
represented by checkbox.
This is a problem, when domain objects are not instantiated by action itself,
but loaded from somewhere else with already present state ( for example from database
via hibernate )
Proposed solution for this problem
1. Enhance simple checkbox template to provide marker false value
2. Provide additional interceptor taking care of marker values
Patches ( while files actually, as I use custom version ) are attached
|
|
Description
|
It is known, that browser do not send anything for unchecked checkoxes -
thus webwork in current state can not actively set "false" value to boolean fields
represented by checkbox.
This is a problem, when domain objects are not instantiated by action itself,
but loaded from somewhere else with already present state ( for example from database
via hibernate )
Proposed solution for this problem
1. Enhance simple checkbox template to provide marker false value
2. Provide additional interceptor taking care of marker values
Patches ( while files actually, as I use custom version ) are attached |
Show » |
|
use before vanilla parameter interceptor