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 Library Glassfish V3 does not contain the either appserv-jstl.jar or jslt-impl.jar file, as a result when added a JSLT component to a jsp file, <%@taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"%> statement is defined as missing Step to Reproduce: 1. Install NB 6.5 RC build 2. Create a web project 3. Open index.jsp file > drap a JSTL component from the Palette to the index file BUG: The error message displays as "The absolute uri: http://java.sun.com/jsp/jstl/core can not be resolved in the web.xml..."
Change bug component
Peter, can we fix this in patch 1? tnk
yep, we need this in patch2... Fix is trivial: add the modules/web/jstl-impl.jar in the libs While we are on it, we need to verify *all* the possibll tld files and see what we are missing.
sorry, patch1
Isn't this a duplicate of issue 152333 (which I previously requested escalation to NB 6.5 patch status)?
i think this is a dup of issue 153407... Davis: I guess you can verify that the fix that is in the trunk addressed this. You need to verify the other issue, so the fix can be backported into the release65_fixes branch...
Will verify with trunk build
Verify with Netbean IDE Dev today (11/21/08), the problem still occurs,
http://hg.netbeans.org/main/rev/936a8a0c57a7
Did a bug get filed against GlassFish V3 to fix this jar so it adheres to the rules? Can the patch be changed to check to see if the jar being added is already in the list (so we future proof against fixed V3 servers that correctly indicate this jar)?
Still able to reproduce this issue in the latest trunk IDE Build 200812011401
Created attachment 74382 [details] Screen shot
yes. builds produced before the integration time will still be broken. please retry with the Dec. 3 build... to account for time differences.
filed issue in GF tracker: https://glassfish.dev.java.net/issues/show_bug.cgi?id=6867
I had to start from a clean userdir to get the library to be constructed correctly. I will see if I can make the change a bit stronger, so it will take effect in situations where the userdir already has a GF library...
I was wrong. It seems like the trunk build (from hudson http://deadlock.netbeans.org/hudson/job/trunk/4495) has the change but the dev build available from netbeans.org does not have the fix in it... Please try using one of the recent hudson builds...
Could you please let me know from where I can download recent Hudson builds.
This fix is verified in the latest Hudson build 4500(IDE build 20081205031259) (http://deadlock.netbeans.org/hudson/job/trunk/4500/artifact/nbbuild/dist/zip/. Hence changing status to verified
Integrated into 'main-golden', will be available in build *200812050201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/936a8a0c57a7 User: Vince Kraemer <vkraemer@netbeans.org> Log: #153407: JSTL taglibs aren't in the classpath
The fix was ported into release65_fixes repository. http://hg.netbeans.org/release65_fixes/rev/4a94062f9953
Verified with NB 6.5 with updates from UC for Patch2.