WOOHOO!!! Everything now works :D
Thanks again for all the help...
On Wed, 2003-11-26 at 08:09, Kris Schneider wrote:
> Remove the JSTL TLD files from WEB-INF.
>
> Remove the JSTL entries from web.xml.
>
> Use a Servlet 2.4 deployment descriptor:
>
> http://java.sun.com/xml/ns/j2ee";
>
Remove the JSTL TLD files from WEB-INF.
Remove the JSTL entries from web.xml.
Use a Servlet 2.4 deployment descriptor:
http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";
Thanks for the help.
The solution provided fixed the error
java.lang.NoClassDefFoundError: javax/servlet/jsp/tagext/TagLibraryValidator.
JAVA_HOME/jre/lib/ext contained standard.jar and jstl.jar which I
moved/deleted.
The other JAR files in JAVA_HOME/jre/lib/ext are:
dnsns.jar ldapsec.jar l
Anna Lissa Saupan wrote:
Thanks for the help.
I've been toiling away with the suggestion mentioned below the last few
days, migrating my JSTL1.0/TC 4.* to JSTL1.1/TC5.*, and I still cannot
make it work :( So, I tried to run a really simple webapp to test if
the JSTL Core library will run on my
Thanks for the help.
I've been toiling away with the suggestion mentioned below the last few
days, migrating my JSTL1.0/TC 4.* to JSTL1.1/TC5.*, and I still cannot
make it work :( So, I tried to run a really simple webapp to test if
the JSTL Core library will run on my server. Unfortunately, e
If you're using TC 5, you should also be using JSTL 1.1. Instead of putting the
JSTL JAR files in $CATALINA_HOME/common/lib, put them in your app's WEB-INF/lib
directory. Note that the taglib URIs have changed between JSTL 1.0 and 1.1. For
example:
1.0:
http://java.sun.com/jstl/core
1.1:
http://j
Thanks for the help.
I did what you suggested. I deployed the application-examples.war that
came with the JSTL distribution, which runs properly. It was also
suggested that:
CLASSPATH=$CLASSPATH:$JAVA_HOME/lib/*.jar:$JAVA_HOME/jre/lib/*.jar:$AXISCLASSPATH
cannot be properly parsed by Linux/Unix.
Your classpath shouldn't matter. The TC startup script will ignore it and build
its own. Have you tried deploying the standard-examples.war application that
comes with the JSTL distribution? Have you modified either your TC or JDK
install? For example, by adding or removing JAR files, perhaps for X
