It make little sense to do it the Husted way and have multiple image bean buttons to represent which html:image was selected. IMHO, that approach is too much like hard coding.
I for one cannot imagine why you would want a button value to be dynamic other than to present i18n options or other image issues. I cannot, that is, imagine why you would not want the issue of whether it was a "submit" or "reset" or "clear" etc. button to be dynamic. Maybe you have a use case I am not thinking about. IMHO that the only thing you need to have dynamic is the content, not the function of the button, e.g. to make what the button looks like dynamic but what the button does static. I think this was Ted's approach too. I mean I think Ted and I have the same approach on that, even though this solution is a lot more convoluted than Ted's. I should say that I am not sure which of Ted's solutions you are talking about. He has more than one. Some use JavaScript, etc.
Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
