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.
The latest version of the pre-release JBoss plugin (the one which is scheduled for Netbeans 6.5 patch 2) does not add the JSF API located in {conf.dir}/deploy/jbossweb.sar/jsf-libs to the server library's classpath. Since JBoss 5 is a fully JEE5-compliant server I believe the plugin should do that.
I forgot to add: This is definitely not a show-stopper, it just feels like something is "missing". A temporary workaround is to add the JSF APIs manually to the project's classpath.
actually it is not only JSF, but also JPA cannot be used. The following jars should at least be added to the classpath for JBoss 5: common/lib/ejb3-persistence.jar common/lib/hibernate-annotations.jar common/lib/hibernate-commons-annotations.jar common/lib/hibernate-core.jar common/lib/hibernate-entitymanager.jar <server>/deploy/jbossweb.sar/jsf-libs/jsf-api.jar <server>/deploy/jbossweb.sar/jsf-libs/jsf-impl.jar (probably more are needed, but these will make compilation of JPA code work). Workaround for the current plugin: copy all these jars to the <server>/lib directory. This will make the netbeans JBoss plugin add the jars to the server runtime library so they are available at compile time. If you copy to a server that is already part of your project, close and restart netbeans to make it update the project classpath. The only thing I am not able to make a workaround for yet is a client application: you are only allowed to choose J2EE 1.4 and not J2EE 5 :( Strangely the ejb and war projects are J2EE 5 projects, just not any client project I create :s