Right, that has sorted the problem with the form, thanks for the help. I'm wondering why that tag was put there in the first place, what could have been the reasoning behind that? I'm hoping that removing it won't have implication elsewhere in the process...
Slattery, Tim - BLS wrote: > >> We have a struts form, and we need to have a styleId element >> (which translates into a standard HTML id element). When we >> include it, the page breaks, with no errors logged, just a >> blank page. If we leave it out completely, when the page >> loads an id element has been included, with the value set to >> the name of the form as defined in the struts-config file. >> That's not id we need! > > I assume you're using XHTML (either xhtml="true" in the Struts html > element or the <html:xhtml/> tag). Normally Struts will create a "name" > attribute for the form tag that contains the form bean name. But in the > xhtml spec, the form tag doesn't have a "name" attribute, so Struts puts > the form bean name into an id attribute instead. As you've seen, if you > try to specify an ID tag, Struts dies. > > > -- > Tim Slattery > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/styleId-attribute-in-html%3Aform-tf4607534.html#a13158694 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
