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: | Can't create web project with JSF framework on Tomcat 6.0 | ||
|---|---|---|---|
| Product: | javaee | Reporter: | Petr Blaha <blaha> |
| Component: | JSF | Assignee: | issues@javaee <issues> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | CC: | jglick, pjiricka |
| Priority: | P2 | Keywords: | REGRESSION |
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
Petr Blaha
2009-02-05 16:21:25 UTC
Looks like the reason is that the JSF library is not registered in the IDE, which is also visible when you switch to the Libraries tab (when JSF framework is selected on the Frameworks step of the wizard). Also, when you go to Tools -> Libraries, JSF is not present. Also when you browse the NB directory structure, under enterprise5/modules/ext/jsf-1_2/, only jsf-api.jar is present. In NB 6.5, this directory contained the entire JSF implementation, i.e. 6 jar files. This is a regression caused by Jesse's removal of the JSF reference implementation module: http://hg.netbeans.org/main/rev/670e0679da5c (besides the fact that this module is autoload, so it was broken already after moving VisualWeb to autoupdate.) What is the best way to fix this? Maybe web.jsf should require (OpenIDE-Module-Requires) a JSF implementation, which would be provided (OpenIDE-Module-Provides) by web.jsf12ri? Would that work even web.jsf12ri is autoload? Petre B, do you think this is an M2 stopper? It's not considered as M2 stopper but should be fixed in next Milestone. Do you have no one evaluating issues? As noted in the original issue, the library would have been missing even before VW was moved to AU, for anyone simply not running VW modules. *** This issue has been marked as a duplicate of 157578 *** > Do you have no one evaluating issues? Who do you mean by "you"? If you mean "your team", then yes, we have "someone" evaluating issues, in these five areas: http://quality.netbeans.org/dashboard/nb70/ruby.html http://quality.netbeans.org/dashboard/nb70/web.html http://quality.netbeans.org/dashboard/nb70/weblanguages.html http://quality.netbeans.org/dashboard/nb70/php.html http://quality.netbeans.org/dashboard/nb70/groovy.html i.e. some 750 P3 bugs total. And now there is a 6th area with 300+ P3s: http://quality.netbeans.org/dashboard/nb70/j2ee.html So you are right, no one has been evaluating issues in this area for the last several weeks, and I am not going to apologize or feel guilty about it. Sure, no offense was intended. I could have marked the original issue P2 for higher visibility but it seemed inappropriate for something that was not obviously a problem and seemed to have been the way it was for some time already. |