Well, since it was me who added the note .. Pretty long time ago, I encountered some weird behaviour doing some work on the (client side) validation, on a now discarded WW project.
From that moment on I always used either camelcase naming style, or
Unfortuneatly, I have no easy way of retrieving that old project, and since I wasn't too sure what the exact cause was (it was a javascript error, I believe a function name that somehow relied on underscores, since it went away when renaming the method), I didn't file a bug report. But I thought I would add it to the wiki for S2 as a warning anyways.
I'm trying to reproduce the problem here, and I'll post an issue once I can find it. Update; well, found it .. turns out I was wrong, and it's not the underscore notation that's giving problems - but using dashes does. I now also recall the underscore (replacement) was a quick hack to get the dash problem away. I'll update the wiki, sorry about the fuss. Phil On 3/5/07, Ted Husted <[EMAIL PROTECTED]> wrote:
* http://struts.apache.org/2.x/docs/action-configuration.html > underscore notation will cause problems with the generated > javascript for certain tags and themes Do we have a better idea of which tags and which themes? We had been presenting underscores in names as a recommended practice when using S1/Cocoon-style wildcards. If we can't fix the tags and templates, then we need to revisit the conventions used by the MailReader application. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- iDTV System Engineer "Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." - John F. Woods --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
