Community
Participate
Working Groups
In the "Component" tab of the faces config editor, the user can open the sectios for "Components", "Converters" or "Validators" and select the "Add" button. Doing so creates a new empty instance of the respective configuration. However, some of the fields of these configuration elements need to be populated for the configuration to be correct. This is even more noticable in 1.2 because schema validation flags these elements as errors.
Triaged for WP 2.0.
I believe this would be better handled with a wizard on hitting the "Add" button, much like what we currently have for managed beans. By using a wizard, we can validate that we have correct information before updating the model. This change effectively pushed this out of scope for the WTP 2.0 release.
A wizard may be the best way but for now I think reasonable non-breaking defaults are good enough. Each of the types of elements that need defaulting have impls available on the classpath if a runtime is installed (i.e. UIInput for components). This will at least ensure that the editor is not creating malformed configurations.
Deferred due to lack of resources
