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 147373 - [65cat] JSF application: The absolute URI cannot be resoleved
Summary: [65cat] JSF application: The absolute URI cannot be resoleved
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-16 13:46 UTC by vanob
Modified: 2008-09-20 22:35 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
messages.log (40.39 KB, text/plain)
2008-09-16 13:47 UTC, vanob 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vanob 2008-09-16 13:46:58 UTC 
[ BUILD # : 200809151401 ]
[ JDK VERSION : 1.6.0 ]

Product Version: NetBeans IDE Dev (Build 200809151401)
Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b15
System: Windows XP version 5.1 running on x86; Cp1252; en_ZW (nb)

Just created new web application.
Pointed Glassfish V3 as a server.

the system created welcomeJSF.jsp and it shows the error for the line
<%@taglib prefix="f" uri="http://java.sun.com/jsf/core"%>

The absolute uri: http://java.sun.com/jsf/core cannot be resolved in
either web.xml or the jar files deployed with this application
Comment 1 vanob 2008-09-16 13:47:56 UTC 
Created attachment 69946 [details]
messages.log
Comment 2 Petr Jiricka 2008-09-19 16:49:52 UTC 
Confirmed, my steps to reproduce are:
1. Create a new Java web application
2. Specify GlassFish v3 as the target server and Java EE 5 as the spec version
3. On the Frameworks panel, add (non-visual) JSF framework.
=> welcomeJSF.jsp shows the error

This only happens with GF v3, not other servers. The reason is that GlassFish v3 does not expose JSF implementation on
its classpath (to check, expand the Libraries -> GlassFish v3 Prelude node under project node). It only exposes the JSF
API. The workaround is to add JSF 1.2 in the Libraries panel of the project properties. This issue is quite serious,
changing priority to P2.

The fix should be either that GlassFish v3 exposes jsf-impl*.jar on its classpath, or the JSF framework module should
adjust the classpath when creating the project. I think the former is preferable, hence reassigning to GlassFish.
Comment 3 Vince Kraemer 2008-09-20 22:35:21 UTC 
I just did a pull and rebuild.

I am using promoted GF V3 b25.

I cannot reproduce this issue.

I had done a fair number of changes yesterday to account for the disappearance of javax.javaee...jar from the V3
distribution between promoted-24 and promoted-25.

That may be the reason I cannot reproduce the issue.  Please reopen if you can reproduce the issue with a NB build post
younger than 20080920, against a promoted build younger than promoted build 24.