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: | init method of Session and Page bean not called when using Tomcat 5.5.20 and higher | ||
---|---|---|---|
Product: | obsolete | Reporter: | Yousuf Haider <yousufh> |
Component: | visualweb | Assignee: | _ potingwu <potingwu> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | potingwu |
Priority: | P2 | Keywords: | TOMCAT |
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
URL: | http://issues.apache.org/bugzilla/show_bug.cgi?id=42354 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Server Log
Server Output |
Description
Yousuf Haider
2007-05-21 18:51:07 UTC
Created attachment 42609 [details]
Server Log
Created attachment 42610 [details]
Server Output
UPDATE: It turns out that this is actually a Tomcat bug that was introduced in Tomcat 5.5.20. What is happening is that if the webapp is stored at a directory that has spaces in it then Tomcat is not able to pick up jars in the WEB-INF/lib folder. Tomcat has a method that returns the paths to all jars with tlds in them but when Tomcat is scanning for these jar files in the WEB-INF/lib folder it is getting the file paths containing '%20' instead of spaces and it is unable to convert the '%20' into spaces. As a result it concludes (wrongly) that there are no jars in the folder. The workaround is to place the webapp in a path with no spaces in it. In that case the project works fine and the table is displayed with data in it. You don't even need to place the jsf and jstl related jar files in the $TOMCAT/common/lib folder. It picks up the jar files from the webapps WEB-INF/lib folder as it should have always been doing. Here is the link for the bug on Tomcat's website: http://issues.apache.org/bugzilla/show_bug.cgi?id=42354 Its marked as fixed in nightly build and the fix will be integrated in Tomcat 5.5.24 apparently. Assigning keyword TOMCAT. marking as invalid since its not a netbeans issue but a tomcat bug. |