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.
this bug has been previously reported under id=75103, marked as solved and it didn't appear to exist in NetBeans 6.8 but I've recently upgraded to 6.9 and now to 6.9.1 and the bug reappears. synopsis: when using jsp with jstl and building with jsp precompile the following error appears: org.apache.jasper.JasperException: file:C:/code/gf/JSTLWUT/build/web/index.jsp(5,61) PWC6188: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application org.apache.jasper.JasperException: PWC6188: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application C:/code/gf/JSTLWUT/build/web/index.jsp(5,61) C:\code\gf\JSTLWUT\nbproject\build-impl.xml:558: Java returned: 1 BUILD FAILED (total time: 0 seconds) steps to reproduce: 1. in netbeans file -> new Java Web App 2. i've chosen glassfish v2 and java EE 5 2a. check the project libraries -> glassfish v2.x -> appserv-jstl.jar is there 3. add this: <%@taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> 4. go to project properties, build/compiling, check 'Test compile all JSP files...' 5. build the project to see the error temporary solution: 1. libraries -> add jar/folder -> add appserv-jstl.jar 2. build the project to make sure all jsps are correct however the .war file contains an unnecessary jar so let's remove it: 3. remove the library 4. uncheck 'test compile...' 5. clean and build
I experience a similar issue using my own taglibs. Because the taglibs are used by a wide variety of applications on our server and also provide server level jndi resources, the libraries themselves are deployed on the server in the domain/lib directory. The taglib descriptors are in a jar that is packaged with each web application (because glassfish no longer searches domain/lib for tlds in jars), but the classes themselves are in a jar that is referenced, but not packaged with the application. Jasper (in netbeans) throws an exception about not finding the taglibs because it doesn't include the referenced (but not packaged) jars in the classpath apparently. If I change the project settings to package the jar, then precompilation of jsps works without issue. I then have to uncheck the package option before deploying. It seems jasper should include the referenced jars in its classpath during precompilation.
*** This bug has been marked as a duplicate of bug 192308 ***