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.
I installed RC1 of NetBeans 3.4. I created a new webmodule and copied all JSTL 1.0.1 required libraries (downloaded from jakarta.apache.org). into the WEB-INF/lib directory. I created the following JSP page: =============PAGE START==================================== <%@page contentType="text/html"%> <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" % > <%@ taglib prefix="x" uri="http://java.sun.com/jstl/xml" %> <c:import url="/wapclick.xml" var="xml"/> <c:import url="/wapclick.xsl" var="xsl"/> <html> <head><title>JSP Page</title></head> <body> <x:transform xml="${xml}" xslt="${xsl}"/> JSTLTest </body> </html> ======================PAGE END======================== The page compiles OK, but when I run it using the internal Tomcat 4.0 web server, I get an error stating that Tomcat cannot load the crimson XMLreader. The crimson.jar is in the lib/ext directory of my NetbeansIDE installation, but it is not in the common/lib of the Tomcat installation that comes with NetBeans 3.4 RC1. Copying the crimson.jar solved the issue. Question remains: why is crimson.jar required? When I look at the JWSDP 1.0 installation (Java Web Services Development Pack from Sun), this also comes with a Tomcat version and this does not include nor requires crimson.jar. The sample above runs OK using the JWSDP Tomcat installation. regards Ronald Lips AtoBe B.V. ronald.lips@atobemobile.com
I tried to reproduce this using the example from the JSTL sample app on Win2K but couldn't. Could you let us know which JDK you use? Also, if you could try the following: 1) Before starting the IDE, go to lib/ext and rename crimson.jar to crimson.raj or something like that. Remove crimson.jar from common/lib or lib/ or wherever you placed it on the server. Start the IDE, compile the JSP and see if it executes now. 2) Alternatively (with crimson.jar in place in the IDE but not on the server), make a change to the JSP which forces the server to recompile it. Don't compile it from the IDE, start the server and access the page from the browser. Does it still not work? If you could let us now the results of these tests, it will help us pinpoint the cause. Thanks, Ana
It seems that the bug has some relation to 22712.
Sorry, for the late response, but I was on holiday. I will try and execute the actions proposed ASAP. I am using JDK version 1.4.0_01
This bug was particular to the tomcat that was shipped with 3.4. (4.0.1, I think). It no longer occurs with 3.5.
VERIFIED