- This topic has 5 replies, 2 voices, and was last updated 20 years, 3 months ago by Riyad Kalla.
-
AuthorPosts
-
TomMemberHi –
I am running Eclipse 3.0.0 and MyEclipse 3.8 Beta-2 on Red Hat AS 3.
Deploying a project to Resin 3.0.8 gets the error: `http://java.sun.com/jsf/html’ has no matching taglib-uri.
Eclipse does not show any error icons on the JSP pages.
The file taglib html_basic.tld is in WEB-INF.
Adding the <taglib> block below to the end of web.xml has no effect, but I see multiple formats called out at the Resin site for <taglib>, which also suggets placing it in resin.conf, and Resin also says TLDs should be automatically found in WEB-INF, which other MyEclipse posts seem to corraborate, so I am unclear about what is correct – and also unclear whether this could be a JSP 2.0 issue.
The block I added at the end of web.xml is below, along with more detailed sysem inffo.
Thanks in advance for sharing your much appreciated knowledge.
Tom
<taglib>
<taglib-uri>
http://java.sun.com/jsf/core
</taglib-uri>
<taglib-location>
/WEB-INF/jsf_core.tld
</taglib-location>
</taglib><taglib>
<taglib-uri>
http://java.sun.com/jsf/html
</taglib-uri>
<taglib-location>
/WEB-INF/html_basic.tld
</taglib-location>
</taglib>MyEclipse Forum post System information:
Linux system info:
Red Hat EL AS 3.0 Linux
Eclipse version and build id: 3.0.0 – 200406251208
MyEclipse version and build id: 3.7.202
Eclipse and MyEclipse are freshly installed (by a user, not root)
Added plugins: Dr Java 0.9.4
Maven plugin in <eclipse>/plugins is like org.eclipse.pde…
Using JDK and installedJRE j2sdk1.4.2_04
Using Resin 3.0.8
There do not seem to be current entries in file <workspace>/.metadata/.log
Riyad KallaMemberTom,
This does sound strange your URIs and what you did look correct.Do you have another server to test deployment to? Can you search the Resin dir to see if it includes its own JSF libraries (maybe older 1.0 versions)? Also this shouldn’t be a JSP 2.0 issue because according to the TLDs for the JSF libs, they are JSP 1.2 compliant.
Also you shouldn’t need the <taglib> entries in your web.xml file because the tlds are included in the META-INF dir of the jsf-impl.jar file which should be in your WEB-INF/lib directory of your project.
TomMemberThanks Riyad –
Yes, this deploys to Tomcat fine…and stranger yet, it used to work in Resin, and I looked, and there are only three ‘*jsf*’ files in <resin_install>, which also exist in <workspace/project>, with the same size and sum in both places (listed below).
In addition to this error on index.jsp, which results from surfing the project “Path” directory and clicking WebRoot, there is a 404 error “/Bookshelf/faces/index.jsp was not found on this server” (“/Bookshelf” is the project “Path” & web.xml specifies: <url-pattern>/faces/*</url-pattern>).
Incidentally, I did not do a make configure before running Resin, and I have not changed resin.conf (there is no “<jsp fast-jstl=’false’/>”), and no JSF jar files appear in Window – Preferences – MyEclipse – Application Servers – Resin – Paths…..although a number of others are appended to the classpath.
Thanks again in advance for any clues!!
Maybe this is a side-effect of a project name refactor which I did and then backed out….
FYI: http://www.caucho.com/resin/ref/taglib.xtp
364344 58066 356 <workspace>/<project>/WebRoot/WEB-INF/lib/jsf-api.jar
364344 58066 356 <resin-3.0.8>/deploy/test/WEB-INF/lib/jsf-api.jar695507 04735 680 <workspace>/<project>/WebRoot/WEB-INF/lib/jsf-impl.jar
695507 04735 680 <resin-3.0.8>/deploy/test/WEB-INF/lib/jsf-impl.jar24514 30952 24 <workspace>/<project>/WebRoot/WEB-INF/jsf_core.tld
24514 30952 24 <resin-3.0.8>/deploy/test/WEB-INF/jsf_core.tld242713 36536 238 <workspace>/<project>/WebRoot/WEB-INF/html_basic.tld
242713 36536 238 <resin-3.0.8>/deploy/test/WEB-INF/html_basic.tld@support-rkalla wrote:
Tom,
This does sound strange your URIs and what you did look correct.Do you have another server to test deployment to? Can you search the Resin dir to see if it includes its own JSF libraries (maybe older 1.0 versions)? Also this shouldn’t be a JSP 2.0 issue because according to the TLDs for the JSF libs, they are JSP 1.2 compliant.
Also you shouldn’t need the <taglib> entries in your web.xml file because the tlds are included in the META-INF dir of the jsf-impl.jar file which should be in your WEB-INF/lib directory of your project.
Riyad KallaMemberI was hoping this didn’t work on Tomcat then we would atleast have something to run with… but if this works on Tomcat and not on Resin, then I’d say there is deinfately a config issue, and I don’t know anything about Resin to help this much…
Can you do a fresh Resin install into a new dir and try and deploy the app there? did that work? Can you try and do a packaged deployment, deploy it to Tomcat and Resin and see if they both work?
TomMemberThanks Riyad!!
Re-installing Resin 3.0.8 as you suggested fixed the problem, and the JSF taglibs are found no with no problem, and with no changes to web.xml or resin.conf.
Riyad KallaMemberThanks for closing the loop Tom, I’m glad it worked.
-
AuthorPosts