Make sure all your frameworks have Property files. Even if they are empty. For some reason WO on Tomcat checks every framework for a property file and fails if it doesn't find one.
I had this problem and the solution was to create empty property files in the frameworks that don't normally have them. -daryl On 2010-11-09, at 9:35 AM, Michael Gargano wrote: > So, I've given up on getting my app deployed to W2K3. Direct Connect > works fine, but there's definitely an issue with the Apache adaptor. > (*sigh*) So, I moved on to Tomcat 6 since I need this app deployed by > tomorrow the latest. I changed my build settings for servlet deployment, and > told it to auto generate the web.xml. But when I deploy to tomcat on a > windows box (from my mac) I receive this error... > > Servlet WOServletAdaptor is not available > > So I checked that the JavaWOJSPServlet_client.jar is in the WEB-INF/lib > directory and I even tried adding it to the classpath of the web.xml without > success. > > Do the variables WOROOT, LOCALROOT, and WOINSTALLROOT even do anything since > the frameworks are all bundled in the war? > > I don't think I've ever gotten my war to deploy. I must be missing something. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [email protected]
