Re: Dreaded 404 - Servlet WOServletAdaptor is not available error

From: Jonathan Miller (johnnypuuno..ac.com)
Date: Mon Jun 18 2007 - 17:17:39 EDT

  • Next message: Joshua Archer: "Re: Building frameworks in Eclipse vs. Xcode"

    Hi,

    Got it working - sort of...

    By hand I edited the new web.xml to look like the old web.xml. The
    main difference being:

    //NEW
       <context-param>
         <param-name>WOClasspath</param-name>
         <param-value>
         WEBINFROOT/Resources/Java/
    WEBINFROOT/Resources/Java/vx30messenger.jar
    WEBINFROOT//Library/Frameworks/JavaEOAccess.framework/Resources/Java/
    javaeoaccess.jar
    WEBINFROOT//Library/Frameworks/JavaEOControl.framework/Resources/Java/
    javaeocontrol.jar
    WEBINFROOT//Library/Frameworks/JavaFoundation.framework/Resources/
    Java/javafoundation.jar
    WEBINFROOT//Library/Frameworks/JavaJDBCAdaptor.framework/Resources/
    Java/javajdbcadaptor.jar
    WEBINFROOT//Library/Frameworks/JavaWebObjects.framework/Resources/
    Java/javawebobjects.jar
    WEBINFROOT//Library/Frameworks/JavaWOExtensions.framework/Resources/
    Java/JavaWOExtensions.jar
    WEBINFROOT//Library/Frameworks/JavaWOJSPServlet.framework/Resources/
    Java/javawojspservlet.jar
    WEBINFROOT//Library/Frameworks/JavaXML.framework/Resources/Java/
    javaxml.jar
    </param-value>
       </context-param>

    //OLD

       <context-param>
         <param-name>WOClasspath</param-name>
         <param-value>
         WEBINFROOT/Resources/Java/
    WEBINFROOT/Library/Frameworks/JavaEOAccess.framework/Resources/Java/
    javaeoaccess.jar
    WEBINFROOT/Library/Frameworks/JavaEOControl.framework/Resources/Java/
    javaeocontrol.jar
    WEBINFROOT/Library/Frameworks/JavaFoundation.framework/Resources/Java/
    javafoundation.jar
    WEBINFROOT/Library/Frameworks/JavaJDBCAdaptor.framework/Resources/
    Java/javajdbcadaptor.jar
    WEBINFROOT/Library/Frameworks/JavaWOExtensions.framework/Resources/
    Java/JavaWOExtensions.jar
    WEBINFROOT/Library/Frameworks/JavaWOJSPServlet.framework/Resources/
    Java/javawojspservlet.jar
    WEBINFROOT/Library/Frameworks/JavaWebObjects.framework/Resources/Java/
    javawebobjects.jar
    WEBINFROOT/Library/Frameworks/JavaXML.framework/Resources/Java/
    javaxml.jar
    WEBINFROOT/VX30Messenger.woa/Contents/Resources/Java/vx30messenger.jar
    </param-value>
       </context-param>

    Now the application launches and runs normally. Before I start
    working on this further - is this a bug with WOLIPS? Or can I alter
    my build script to fix this?

    Best

    Jon

    On Jun 18, 2007, at 11:05 AM, Stephen Edwards wrote:

    > Jonathan Miller wrote:
    >> I just purchased a new computer and downloaded and installed the
    >> latest Eclipse/WOLIPS. Previously I had been running a custom
    >> build of WOLIPS that has SSDD support for Tomcat.
    >
    > Presumably, your build.xml file is unchanged from before, right?
    >
    > From your classpath, it looks like you are not using Project WONDER.
    > Is that correct?
    >
    > Often, this symptom is the result of a failure during app
    > initialization. The WOServletAdaptor usually spits out some
    > exception info on System.out (no, not controllable by NSLog
    > settings or log4j stuff--just a plain old System.out.println())
    > before throwing a second exception to indicate servlet
    > initialization failed. This would appear after the classpath
    > line you cited. Is there anything else useful in your log file?
    >
    > -- Steve
    >
    > ----------------------------------------------------------------------
    > -----
    > Virginia Tech, CS Dept. Web-CAT: Web-based Center for Software
    > Testing
    > 660 McBryde Hall (0106) Automatic grading using student-written
    > tests
    > Blacksburg, VA 24061 USA http://web-cat.sourceforge.net/
    > (540)-231-5723 http://people.cs.vt.edu/~edwards/



    This archive was generated by hypermail 2.0.0 : Mon Jun 18 2007 - 17:18:55 EDT