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.

Bug 182313 - create tests for creating WebLogic-based projects with JSF support
Summary: create tests for creating WebLogic-based projects with JSF support
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Tomasz Slota
Depends on:
Reported: 2010-03-18 15:01 UTC by Petr Jiricka
Modified: 2010-10-18 14:56 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2010-03-18 15:01:02 UTC
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
Comment 1 Tomasz Slota 2010-03-19 13:48:53 UTC
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'
Comment 2 Tomasz Slota 2010-03-19 16:47:23 UTC
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:

Anyways, the current IDE user experience is unacceptable, I am investigating more..
Comment 3 Tomasz Slota 2010-03-23 15:38:10 UTC
Reassigning to phejl as this is not really editor issue
Comment 4 Petr Jiricka 2010-03-31 16:37:02 UTC
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:


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?
Comment 5 Petr Jiricka 2010-03-31 16:39:56 UTC
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).
Comment 6 Petr Hejl 2010-04-08 14:33:00 UTC
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).
Comment 7 Tomasz Slota 2010-05-11 12:11:24 UTC
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...
Comment 8 Petr Jiricka 2010-05-12 13:41:43 UTC
I can confirm it works for me as well.
Comment 9 Tomasz Slota 2010-05-12 14:55:18 UTC
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.
Comment 10 Petr Jiricka 2010-10-18 14:56:32 UTC
No bandwidth for this.