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.
build 200705281800 jdk1.6b105 1) Register Tomcat 6 2) Create new Web project with VW JSF Project is created, but visual editor shows numbers of errors, as javax.faces.* packages are missing. Workaround:Add JSF 1.1 library
Created attachment 42942 [details] how it looks
This is a known requirement for Tomcat 6; by adding the required JSF RI libraries into Tomcat 6 lib directory. It's not a bug.
I filed the same issue over here some time ago: http://www.netbeans.org/issues/show_bug.cgi?id=101689
If i want to CREATE project on any other server with Netbeans, I can do it and I don't get similar view, as this action is siccessful for every other combination of servers and J2Ee version. Why should be Visual Web Project different? DEPLOYMENT is another thing. If JSF library is missing, why don't you add it to the project upon creating and hence clean these errors?!
This issue isn't same as 101689, as it's not about deploying.
If this is not for deployment, then this bug will be 'WONTFIX'! The error/warning mesg in the designer is for 'INFORMATION' that returns from the Java compiler. It's not a bug and it's by design. If you think the designer shouldn't show this!!!, then you should file against the visual editor. And no, we can't auto-bundle any missing libraries into the project, it's not correct for a product point of view. We even have plan not bundle JSF 1.1 project and will remove this bundle scheme.
Hi all, this is definitely bug since user doesn't change any line in the code and the project is created with errors from beginning. Why you don't add JSF 1.1 library to project classpath when VWP JSF project is created by default. How doees it work when user create standard web project with JSF? Please, feel to reassign to correct component.
Hi, it should be solved soon. Today Radko has committed a code, which should covered this.
Adding the JSF1.1 library will work at design time but on deployment ClassNotFound exceptions will be thrown when the project looks for JSF1.2 specific classes such as javax.faces.application.StateManagerWrapper. The right solution would be to add a new library in the library manager with the jsf1.2 jars (jsf-impl and jsf-api) and then add the newly created library into the project. Also we need to manually add the JSTl 1.1 library in the project as well since it is not added by the IDE by default.
*** Issue 105677 has been marked as a duplicate of this issue. ***
*** Issue 105192 has been marked as a duplicate of this issue. ***
Now Visual Web JSF framework bundles JSF 1.2 RI for Java EE 5 projects if the target servers don't support JSF. And asks users to create/add JSF 1.1 RI for J2EE 1.4 projects.
To Reporter: Could you please verify this issue? Thanks.
v. build 200706241800