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.
Summary: | jsp using JSTL taglib directive can not precompile | ||
---|---|---|---|
Product: | javaee | Reporter: | kRyszard |
Component: | JSP | Assignee: | Anton Chechel <manowar> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
kRyszard
2010-08-21 09:41:28 UTC
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 *** |