Subject: Autodeploying Struts apps from Forte to Tomcat via WARfile -- BROKEN?!? From: "Jeff" <[EMAIL PROTECTED]> === Has -anybody- ever managed to build a Struts-using web app inside Forte or Netbeans AND successfully autodeploy the app using a WARfile created by Forte/Netbeans to a standalone server running Tomcat 4?
I'm ready to throw in the towel and write it off as broken. After three weeks of on-and-off experimentation and process of elimination, I have yet to get a warfile-autodeployed Struts app created by Forte to work under Tomcat. I've tried both path mapping and extension mapping, with a variety of deployment scenarios, and seem to inevitably wind up with one of three errors: - A 403 error because Tomcat didn't properly associate the path with the Action servlet ex: /path/* mapped to Action servlet, application deployed to "$CATALINA_HOME/webapps/path", "/foo" mapped as an Action Path, browser attempts to launch http://host:8080/path/foo - A 500 error because Tomcat associated the path with Action servlet, but wasn't able to find a matching action path in struts-config.xml ex: /path/* mapped to Action servlet, application deployed to "$CATALINA_HOME/webapps/path", "/foo" and "/path/foo" mapped as Action paths, browser attempts to launch http://host:8080/path/foo or http://host:8080/path/foo.do - A 500 error because the XML parser couldn't parse struts-config.xml ex: application deployed to "$CATALINA_HOME/webapps/path", with "/foo", "/path/foo", AND "/path/path/foo" mapped as action paths, browser attempts to launch http://host:8080/path/foo or http://host:8080/path/foo.do same, but application deployed to $CATALINA_HOME/ROOT I'm convinced Forte is screwing up somewhere, and it's NOT an XML parser issue, because the .war files distributed with Struts -do- work and autodeploy. It's just the web apps autodeployed from Forte-built warfiles that invariably crash and burn. Incriminatingly (for Forte) enough, if I unpack the Struts demo apps using Winzip, delete the META-INF directory, mount the remaining directory into Forte and build it... I get the same result: it works in Forte's Tomcat, but crashes and burns upon deployment to a standalone Tomcat. If you've actually gotten a Struts app built with Forte to autodeploy successfully... * did you use path or extension mapping? What value did you use (a snip from web.xml would be great) * did you deploy it by dumping the .war file into Tomcat's webapps dir and letting it autodeploy into a subdirectory of webapps named after the .war file, or did you have to do something special? * give me a sample URL (http://hostname:8080/...) that worked, along with its corresponding entry in struts-config.xml (<action... path="/..."). Were you able to use the same root-relative URL in both Forte and Tomcat? In other words, did you find some "/arbirtary_path/path_mapped_to_ActionServlet/path_defined_in_struts-config. xml" that worked under Forte's built-in Tomcat AND an external Tomcat? On the other hand, if you're fairly confident that Forte's warfile creation is simply broken with respect to Struts apps, I'd like to know that once and for all too. Likewise, if somebody has a sample Ant file specific to the task of deploying a Struts-using app from Forte to Tomcat, I'd love to see it/them, because I'm pretty sure it's the only way I'm ever going to get it to work anytime soon. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
