Josh McDonald wrote:
styleId, reference the taglib docs:
http://struts.apache.org/struts-doc-1.2.x/userGuide/struts-html.html#form
Ah thanks I didn't see that.
Or to generate a name="" that's not based on the name of the form
bean?
I'm not sure why you'd want to that.
So I can have two forms that use the same form, mainly. Otherwise I
need multiple entries in the "class->bean name" mapping section of the
config file, which just seems unecessary to me.
Just trying to clean up this application, it's got more duplicated code
than anything I've seen in a long time.
You can apply different validation rules for the same action form by
tying your validation to the action mapping path instead of the form, if
that helps... In other words, instead of saying 'form X has validation
rules Y', you can say 'action X has validation rules Y' and then use the
same form with different actions, applying different different
validation rules to each one.
Is that what your concern was, or are you trying to achieve something
different?
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
