[jBoss-User] TagLibs Problem Solved - culprit JETTY_HOME

[Tim White]

Thanks to Richard Backhouse for pointing me in the right direction to
solve this one.

The problem: When running jBoss with either Tomcat or Jetty, taglibs
don't work.
The symptom: The taglibs themselves can't be found, looks like the wrong
parser is being invoked.
The solution: Don't have JETTY_HOME set to a valid Jetty installation
before running jBoss-Tomcat.

Why:

In the run.sh that comes with jboss_tomcat:

if [ "${JETTY_HOME}X" != "X" ] ; then
    if [ -x $JETTY_HOME ] ; then
        echo "Adding jar files in ${JETTY_HOME}/lib to CLASSPATH"
        CLASSPATH="$CLASSPATH:${JETTY_HOME}/lib"
        CLASSPATH="$CLASSPATH:${JETTY_HOME}/lib/com.sun.net.ssl.jar"
        CLASSPATH="$CLASSPATH:${JETTY_HOME}/lib/javax.servlet.jar"
        CLASSPATH="$CLASSPATH:${JETTY_HOME}/lib/com.mortbay.jetty.jar"
        CLASSPATH="$CLASSPATH:${JETTY_HOME}/lib/org.apache.jasper.jar"

        # Add the tools.jar file so that Jetty can find the Java
compiler.
        CLASSPATH="$CLASSPATH:$JAVA_HOME/lib/tools.jar"
    else
        echo "JETTY_HOME is set, but is an invalid directory"
    fi
    JETTY_FLAGS="$JETTY_FLAGS -Djetty.home=$JETTY_HOME"
    JETTY_FLAGS="$JETTY_FLAGS
-Dorg.xml.sax.parser=com.sun.xml.parser.Parser"
fi

Note the inclusion of org.apache.jasper.jar.

Humorously, the run.sh that comes with jboss_jetty DOESN'T include that
stuff.

I'm filing Bugzilla stuff now.

Thanks,

Tim


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]