1 Reply Latest reply on Jan 21, 2005 5:46 PM by Tomasz Nazar

    Problems mapping strut's ActionServlet while using embedded

    Niti Upadhyay Newbie

      Hi,

      I'm kind of new to JBoss. I was handed an application that works in JBoss 2.2 + Standalone tomcat environment. I was asked to move over to latest JBoss technology.

      I downloaded RC2 version of JBoss 4.0.1 and latest struts. When my .ear file is deployed, I don't see any log specifing that ActionServlet was mapped. I even tried to use older version of struts.

      Then I downloaded tomcat version 4.1.31 and deployed the .war file. On doing this, I saw that the ActionServlet was mapped.

      What do I have to do to make JBoss detect the struts information in web.xml. Maybe it can't even find web.xml. For the web-console app that came with JBoss, I see the following log

      2005-01-14 11:03:54,939 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/D:/JBoss-4.0.1_Tomcat-4.1.31/jboss/server/default/deploy/management/web-console.war/ -> file:/D:/JBoss-4.0.1_Tomcat-4.1.31/jboss/server/default/deploy/management/web-console.war/WEB-INF/web.xml

      But, for my app, I don't see any of this.

      Please help me understand how JBoss works.

      Thanks.

        • 1. Re: Problems mapping strut's ActionServlet while using embed
          Tomasz Nazar Newbie

          Hi!

          Last time I did similar with JBoss and Struts application. What I had was properly working version of Struts based application on Tomcat. It was packed as *.war file.

          For my private needs I've applied AOP to my application, but it should make zero difference for your problem.

          I've downloaded latest Jboss AS version 4.0.1. Unpacked. Put my application inside JBOSS_HOME/server/default/deploy/ - actually I've unpacked it into directory name: application.war/

          Started JBoss: ./bin/run.sh -c default

          That's all. It works smooth for me. With Struts of course. I don't use any EJB nor standard DB. But it shouldn't be the reason.

          Check directories once more. Watch the log.. there should be information about deploying your application.

          Regards, Tomasz