3 Replies Latest reply on Jul 2, 2002 5:23 AM by Julian Gosnell

    Deploying jboss on Windows ME

    Saruman White Newbie

      It seems to be working, but... I downloaded the default version of Jboss 3.0.0 installed and started it. I don't see any errors in the log. http://localhost:8082 gives me all the configuration paraphernalia. However localhost:8080 responds with HTTP 404 errors, talking about not finding default context. I honestly tried to deploy a web application through jboss.web:Jetty=0 service, gave it '/myapp' context
      and a directory that contained a jsp and a dummy webapp. Log defintely did something, saying about registering that and this etc. Nothing changed however - still 404. Any ideas - beside installing, say, Windows XP, because I don't see what it has to do with purely local quirks of Java.

        • 1. Re: Deploying jboss on Windows ME
          Joel Vogt Master

          cay you post exactly what your log did say?

          • 2. Re: Deploying jboss on Windows ME
            Saruman White Newbie

            Log says

            15:25:36,150 INFO [Jetty] Registered jboss.web:Jetty=0,WebApplicationContext=0,
            15:25:36,150 INFO [Jetty] Web Application WebApplicationContext[/mywar,file:/C:
            /My Documents/jettydir/mywar.war] added

            Here context in the 1st line actually does not depend on what I specify in the input field.

            The WAR consists of a primitive JSP under /jsp and web.xml (<web-app></web-app>) under /WEB-INF.

            Whatever url I try under localhost:8080 produces

            15:25:08,470 INFO [Jetty] Registered jboss.web:Jetty=0,HttpContext=0,context=/
            15:25:08,470 INFO [Jetty] Started NotFoundHandler in HttpContext[/]

            on the first try and nothing after that. Any ideas?

            • 3. Re: Deploying jboss on Windows ME
              Julian Gosnell Expert

              Don't deploy through through the Jetty MBean, go through the MainDeployer. The Jetty one is for standalone Jetty and will not keep JBoss abreast of what is going on (I shall have to hide it).

              Or simply copy your deployable into your configurations (probably default) deploy directory.

              Good luck,