Community
Participate
Working Groups
This is a follow-on to bug 207589: I just tried the 12/06 WTP 3.0 build and the Axis2 JSPs (added to Web project when the Axis2 facet was addd) are still being flagged as error: Description Resource Path Location Type13The function back() is undefined for the type Array adminheader.jsp a2b/WebContent/axis2-web/include line 39 Validation Message13The function reload(boolean) is undefined link-footer.jsp a2b/WebContent/axis2-web/include line 23 Validation Message13The function submit() is undefined upload.jsp a2b/WebContent/axis2-web line 29 Validation Message13The type Document is not visible upload.jsp a2b/WebContent/axis2-web line 25 Validation Message13The type Document is not visible upload.jsp a2b/WebContent/axis2-web line 29 Validation Message13Void functions cannot return a value link-footer.jsp a2b/WebContent/axis2-web/include line 23 Validation Message13
hi Kathy, I downloaded the newest version of Axis2 to see if these errors still exist, and they don't. It seems that the offending JavaScript listed above has been removed.
I tried with the 2008 11/20 WTP 3.1 driver with Axis2 v1.4.1 and still got the error: Description Resource Path Location Type The function submit() is undefined upload.jsp a2a/WebContent/axis2-web line 30 Validation Message Please note that after re-enabling the JavaScript validation, you would have to manually select the WebContent/axis2-web folder and choose Validation in order to trigger validation. We have programmatically turned off validation of this folder since there are many warnings in the JSP. You would get the same result using WTP 3.0.3 driver as well.
We're seeing this in our adoption of WTP 3.1 as well. We don't have Axis 2 but we rely on the WTP Web services code for sample JSP generation and this javascript error is popping up: "The function submit() is undefined for the type Element"
I'd like to see this fixed for 3.1 M6, for the reasons mentioned in the comments made above.
Eric has seen this on a 3.0.4 version of WTP. This is a regression from WTP 3.0 and contributes to bad out-of-the-box experience for our customers who want to generate and use Web service client sample JSPs.
Marking this as a hotbug for WTP 3.0.4. Adding David Williams to the cc list.
(In reply to comment #5) > Eric has seen this on a 3.0.4 version of WTP. This is a regression from WTP 3.0 > and contributes to bad out-of-the-box experience for our customers who want to > generate and use Web service client sample JSPs. Yen, I've marked this as a hotbug_request for 3.0.4, as per the reasons you've stated.
Regression from fixing bug 241794, which involved moving the JS validator to the V2 framework, but left it enabled by default.
Created attachment 125490 [details] disables JavaScript validation by default
From the PMC questionnaire, this is stop ship by virtue of being a regression. It has been tested by myself, and simply sets the JavaScript validator to be disabled by default. It's as close to zero risk as anything can be.
Released to 3.0.4
I've verified that validation is now off by default. I don't get an error marker in the problems view, and there are no red error decorators on the file or project. But if I open the file in the JSP editor, there is still a red squiggly line under some of my javascript indicating there is an error. If I mouse over the error I see "The function submit() is undefined for the type Element". It looks to me like whatever contributes the error "red underline" is not respecting the preference that turns of JS validation. Should I open a separate bug for this?
(In reply to comment #12) > Should I open a separate bug for this? I think it's covered under bug 174740 .
