Community
Participate
Working Groups
It is very difficult to get type compatibilty validation correct in JSF at designtime. Converters can be applied to tag values using child tags, and the faces configurations can be customized to add converters for classes. There are already several bugs in the system about false positives on type compare validations. In an attempt to alleviate this problem, the default severity for type compatability validations will be lowered from Warning to Ignore. A user may change this preference in the JSF Validations preference page. In addition, the current logic that attempts to provide converter applied validations will be disabled by default. A system/env property will be made available to re-enable. Future work will attempt to improve validations of type compatibility.
Created attachment 167042 [details] Patch This patch: - sets default preference for "Value expression type incompatibility" to Ignore. - disables alternative considered types logic. It may be re-enabled using "jsfCoreEnableConverterValidation" system/env property setting.
* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. Reporting false-positives when validating value expression for type compatibility has been a big source of bugs logged by users and adopters. * Is there a work-around? If so, why do you believe the work-around is insufficient? The workaround is to manually set the preference to ignore the warnings. However, the end user will still incur the cost of constructing the component tree, which can affect performance. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Manual testing. * Give a brief technical overview. Who has reviewed this fix? See description * What is the risk associated with this fix? low
Checked into HEAD 5/5/10
