This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Configuration: Windows 2K Professional Tomcat 4.0.4 FFJ 4.0 CE JDK 1.4.0 Install Tomcat 4.0.4. Fire up the server and look at the "Web applications" box under the Tomcat logo. Select "JSP Examples" and execute any of the examples. They work. Now add this server instance to the IDE in full integration mode. Execute a JSP again. It does not work.
Created attachment 6684 [details] web module log file from server, shows IDEJSPServlet was not available
works for me - Linux / JDK1.3.1 and 1.4.0 too / Tomcat 4.0.4 running with latest NetBeans (almost equal to 3.4B3) with all additional web modules (jspie, monitor, jspdebug, taglibed) Can you attach ide.log and maybe check content of lib, common/lib and server/lib dirs in Tomcat directory? What files are copied here?
Works for me as well on Netbeans3.4. I will investigate it on Orion release.
It seams that for configuration : Forte(Orion release) + Tomcat4.0.4 external server is really missing something. I was able to reproduce the issue. When I changed the IdeMode property to Minimum - jsp from examples was executable. There is some issue with IDEJspServet.
tomcat40-ide.jar and httpmonitor.jar are both in lib, httpmonitorvalve.jar is in server/lib, these are deployed correctly. Will attach the ide.log too, which while it makes interesting reading in general doesn't show anything w.r.t the failed execution (see end). other than that surely the executor shouldn't tell the log what it's doing every time...
Created attachment 6735 [details] ide.log. only the last part pertains to this problem (july 16)
No, Tomcat 4.0.4 does not work with Orion. There are changes in the Tomcat source (namely removal of class org.apache.jasper.JasperError between TC 4.0.4 beta 2 and 4.0.4 beta 3), which prevent the IDE code from working with Tomcat 4.0.4. So there are good reasons why 4.0.4 is not supported in Orion. The question is whether we should consider fixing this for the Sierra release, or for some other update release.
Aha. I thought it was only Tomcat 4.1 that we knew did not work with Orion, not 4.0.4. As far as I remember 4.0.4. wasn't final when we released? I also thought we semi- successfully integrated with 4.0.4beta 3. So what happened between then and the final release that made integration impossible, and how easy would it be to address? Did this make it into the release notes? There have been several requests for this on nbusers so we should make it clear (and fix it for Sierra if that's posssible, IMO).
Also, Radim says that it works on at least one other OS (Linux). Is this only a problem with Win2K Pro?
Apologies for multiple follow ups... It's a little early for me to have more than one thought at any one time... I recommend fixing it if it's done in such a way that the module is agnostic as to whether JasperError exists or not. I assume that this did not make it into the release notes (I was confused because I read Petr's message to say that we'd been aware of this problem for some time). I would suggest that the next time the issue comes up on nbusers (whether the user is asking with reference to ffj or nb) that we explain the situation for ffj.
I think this is the problem of all platforms, not just Win. I don't think this was release noted. Anyhow, I am attaching a patch for the sierra branch (merged from the release34 branch). I verified that Tomcat 4.0.1 continues to work with it in Sierra builds, as does 4.0.3. Radim, could you please review it ?
Created attachment 6812 [details] Patch against the sierra branch
I agree with the patch. Radim
Set target milestone to TBD
Fixed on July 23 - taking the fix from the release34 branch.
Verified in Sierra build 020729_ee.