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.
Related to bug 182282. 1. Register the latest WebLogic server 2. Create a new Java EE 5 application with WebLogic as the target 3. On the Frameworks panel, select JSF and accept the defaults 4. In welcomeJSF.jsp, you see that custom tags are not recognized
Reproducible. There's an error message on the taglib declaration, it says 'the absolute uri cannot be resolved in either web.xml or the jar files deployed with this application'
This seems to be a very old issue, possibly a duplicate of issue 106582 and issue 103508. The issue is caused by the fact that Weblogic requires the JSF libraries to be deployed manually, see: http://download-llnw.oracle.com/docs/cd/E12840_01/wls/docs103/webapp/configurejsfandjtsl.html Anyways, the current IDE user experience is unacceptable, I am investigating more..
Reassigning to phejl as this is not really editor issue
One other thing - I discovered that WebLogic contains just the JSF APIs on the classpath, not JSF implementation. Could this be a problem for the editor? WebLogic by default does not even contain a JSF implementation jar ready to be used. It is included in war file wlserver_10.3/common/deployable-libraries/jsf-1.2.war. When JSF is deployed using the admin command described in the document above, the following files appear under the domain dir: user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/jsf/2ndlrw/WEB-INF/lib/glassfish.jsf_1.2.9.0.jar user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/jsf/2ndlrw/WEB-INF/lib/glassfish.jstl_1.2.0.1.jar user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/jsf/2ndlrw/WEB-INF/lib/javax.jsf_1.0.0.0_1-2.jar user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/jsf/2ndlrw/WEB-INF/lib/wls.jsf.di.jar After that, deployment works. However, after manually resolving the deployment problem this way, the editor still displays the errors. So doesn't the fix still need to be on the editor side?
Regarding the workaround I just described - one has to also add the library-ref to weblogic.xml of course, as described in the document, and remove JSF+JSTL from project's libraries (currently they are added by default because of Alexey's workaround for issue 182282).
Tomas, can you investigate what is really needed on classpath, how is it detected and why the editor does not work for Petr. I was not able to broke it since Alexey's patch (although I removed the libraries).
Surprise - it seems to be working fine now. I am trying to find out what change set fixed the problem and if it's not reproducible under different setups...
I can confirm it works for me as well.
I've tried a few different scenarios and they all work. Instead of of closing the issue I am downgrading it to P3 as I reminder to create functional unit tests for it.
No bandwidth for this.