- This topic has 3 replies, 2 voices, and was last updated 21 years ago by
Riyad Kalla.
-
AuthorPosts
-
Don NelsonMemberNot sure if this is a bug or enhancement request, but when using the jstl core libs, I find that I have to manually add the <taglib> info to the web.xml, even though I’m using the absolute URI for the tablib. Eclipse doesn’t seem to have a problem with it, but Tomcat does when it tries to run the jsp. I get the message:
“org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application”
I would have expected the JSTL extensions in Beta 2 would have taken care of updating the deployment descriptor. Is this supposed to be the case, or am I missing something?
I also have the follownig errors in the eclipse log file (not sure if it’s connected):
!ENTRY de.bb.bje.eclipse 4 1 Jul 15, 2004 16:58:19.418
!MESSAGE JSP Compiler broken
!STACK 0
java.lang.NoClassDefFoundError: javax/servlet/jsp/JspContext
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.getDeclaredMethods(Unknown Source)
at java.beans.Introspector$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.beans.Introspector.getPublicDeclaredMethods(Unknown Source)
at java.beans.Introspector.getTargetMethodInfo(Unknown Source)
at java.beans.Introspector.getBeanInfo(Unknown Source)
at java.beans.Introspector.getBeanInfo(Unknown Source)
at java.beans.Introspector.getBeanInfo(Unknown Source)
at java.beans.Introspector.<init>(Unknown Source)
at java.beans.Introspector.getBeanInfo(Unknown Source)
at de.bb.jsp.JspCC.z(Unknown Source)
at de.bb.jsp.JspCC.u(Unknown Source)
at de.bb.jsp.JspCC.t(Unknown Source)
at de.bb.jsp.JspCC.g(Unknown Source)
at de.bb.jsp.JspCC.t(Unknown Source)
at de.bb.jsp.JspCC.g(Unknown Source)
at de.bb.jsp.JspCC.streamCompile(Unknown Source)
at de.bb.bje.eclipse.support.JspCompiler.streamJspCC(Unknown Source)
at de.bb.bje.eclipse.editors.BJspEditor$1.run(Unknown Source)Thanks much.
Don
System settings:
—————————-
– System Setup ——————————-
Operating System and version: XP
Eclipse version: Version: 3.0.0
Eclipse build id: 200406251208
Fresh Eclipse install (y/n): no
If not, was it upgraded to its current version using the update manager? No
Other installed external plugins: metrics, swt designer, kodo, profiler
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.8b2
Eclipse JDK version: j2sdk1.4.2_05
Application Server JDK version: j2sdk1.4.2_05
Are there any exceptions in the Eclipse log file? see aboveJuly 15, 2004 at 9:52 pm #210194
Riyad KallaMemberDon you are using the incorrect URI, if you open up the standard.jar file that is deployed (JSTL 1.0, not 1.1, we don’t support 1.1 just yet) the URI defined in the TLD files in the META-INF dir is “http://java.sun.com/jstl/core”
Give that a whirl and see if it fixes it.
July 16, 2004 at 5:59 pm #210269
Don NelsonMemberAhhhh – well that could have something to do with it, couldn’t it? 😳 Thanks much – that fixed it!
July 16, 2004 at 6:09 pm #210270
Riyad KallaMemberI’m glad it fixed it.
-
AuthorPosts