- This topic has 19 replies, 4 voices, and was last updated 20 years, 5 months ago by
.
-
Posts
-
I was not sure if I should post this as a separate bug: the input JSP that is generated from the above wizard does not fill in the form action with the Struts action name. For example, in my example I have an Action path called “/courseSearch”. Should the generated JSP have that as the form’s action?
The form’s action currently reads:
<html:form action=”/[ACTION_PATH]”>The above causes the JSP to fail as no such action exists.
Carlos
Carlos,
Yes it should fill in all of that for you, I know we have a previous bug with one of the betas where the generated values were not getting filled in and I believe Scott let us know that this is fixed (or should be fixed in Beta 2). I’m wondering if this is a similar (or the same bug). I will pass it along anyway to verify so we don’t get any wires crossed.Stop being so understanding. It is difficult to stay upset otherwise.
I think it is you who is being understanding. Frankly bugs drive us nuts but based on our development environment we don’t get a chance to excercise every code path before a release (Especially beta) so whenever our users report bugs in a calm and informative manner we really appreciate it. We can sympathize with how damn annoying it can be sometimes when you click a button and the opposite of what you wanted to happen, happens.
I bonked the QA on the dynform prob. It will definitely be knocked out in next week’s beta-2. (I know because I have to fix it – again.) The generated JSP has been fixed in the current codebase and is already in the QA builds.
