On Fri, 18 Mar 2005 08:05:50 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote: > I don't really understand this use case. unless the contents of > <html:form> are hyper-dynamic, you'd need the same form bean to back > it, even if upon submit the thing actually goes to a different > action. I am familiar with the use case that would change the > destination of the "action" property of the form using JavaScript, > but I think you're talking about something different.
It's less about the formbean and more about what the mapping does. A few use cases are when * a form (often a Tile) is used in a wizard and also in a separate case that edits the fields on that screen but not the rest * a generic search form is used to seach several different datasets If I went through some of my old applications, I'm sure I could find several others. I often passed the action in as a bean and rendered via a RTE . -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
