|
Andrew: As for first suggestion: 1) Have the converter use a default value when there is no valueIt is more like suggested default value for this form, it could be a different default in a different form. It is such in my case, where a content created from one link defaults to MENU_ITEM, and if content is created from another link it defaults to another value. So converter may not be a good place to set it, as the same converter will get used at both places. as for the second suggestion: 2) Have the backing bean value never be null (always require that it is set)I could set the defaults in the managed bean as 'usually' different forms will have separate 'managed beans' and defaults could be set there.. But, for this option there is a 'what if' question, what if I am using the same form+managed bean from different links which should result in defaults of different types? As I am writing this, just thinking out loud, it is possible that the different links send params to the managed bean with default values, and the managed bean sets it in 'add' action method before the form is drawn. But the 'what if' question still remains, what if I want a default value to be supplied from jsf for each form (if different forms are using the same managed bean, or Is that not a good idea?)? Is it not possible? Thanks MRather Andrew Robinson wrote: 1) Have the converter use a default value when there is no value or 2) Have the backing bean value never be null (always require that it is set)On Dec 26, 2007 10:48 AM, M Rather <[EMAIL PROTECTED]> wrote: |
- default value of input field not of string type - how to s... M Rather
- Re: default value of input field not of string type -... Andrew Robinson
- Re: default value of input field not of string ty... M Rather
- Re: default value of input field not of strin... Andrew Robinson

