html:javascript behavior when form is not found

2004-02-03 Thread Joe Germuska
Right now, if you accidentally enter a bogus form name in the html:javascript tag, it omits the wrapping script tags, but prints all the javascript anyway. This doesn't seem right, but for some reason I have a feeling that the solutions I'm thinking of are a bit contentious, so rather than

Re: html:javascript behavior when form is not found

2004-02-03 Thread Paul Sundling
I'm not sure if struts itself has a design philosophy, but java itself has the fail fast philosophy. Iterators are one of the most widely cited examples. If something is wrong you want to fail as quickly as possible. A developer should be made aware of the mistake. Leaving a comment is

Re: html:javascript behavior when form is not found

2004-02-03 Thread [EMAIL PROTECTED]
-Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Right now, if you accidentally enter a bogus form name in the html:javascript tag, it omits the wrapping script tags, but prints all the javascript anyway. This doesn't seem right, but for some reason I have a

Re: html:javascript behavior when form is not found

2004-02-03 Thread Joe Germuska
At 1:55 AM + 2/4/04, [EMAIL PROTECTED] wrote: I am all for in-your-face. Tapestry has sort of a built in debugging web page that gives all sorts of stats, on your running web app. The least we can do is Blow up in a loud usefull way. Alright, then; based on your input and Paul's, I'll make it