4 Replies Latest reply on Dec 17, 2002 2:46 PM by s goswami

    HTTP POST

    s goswami Newbie

      Is HTTP POST supported in JBOSS 3.0.4/4.1.12 ? If so , what needs to done ? The following is the error message I get on the client side.

      "java.io.IOException: Connection failure with 405"
      HTTP Method POST is not supported by this URL.

        • 1. Re: HTTP POST -solved (caused by broken hot deploy)
          s goswami Newbie

          I think , the problem is solved. There were two copies of the same Servlet classes in the JBoss jar file and the Tomcat war file. I do not always update the JBoss jar file as that requires a restart (hot deploy is broken in JBoss EJB). The Tomcat war file can be hot deployed. Unfortunately, Tomcat picks up the Servlet class from the EJB jar file rather than the Tomcat war file - I guess that is the price paid for using the same JVM. Although I think it can be corrected.

          • 2. Re: HTTP POST-solved (caused by broken JBoss hot deploy)
            s goswami Newbie

            I think , the problem is solved. There were two copies of the same Servlet classes in the JBoss jar file and the Tomcat war file. I do not always update the JBoss jar file as that requires a restart (hot deploy is broken in JBoss EJB). The Tomcat war file can be hot deployed. Unfortunately, Tomcat picks up the Servlet class from the EJB jar file rather than the Tomcat war file - I guess that is the price paid for using the same JVM. Although I think it can be corrected.

            • 3. Re: HTTP POST
              s goswami Newbie

              I think , the problem is solved. There were two copies of the same Servlet classes in the JBoss jar file and the Tomcat war file. I do not always update the JBoss jar file as that requires a restart (hot deploy is broken in JBoss EJB). The Tomcat war file can be hot deployed. Unfortunately, Tomcat picks up the Servlet class from the EJB jar file rather than the Tomcat war file - I guess that is the price paid for using the same JVM. Although I think it can be corrected.

              • 4. Re: HTTP POST
                s goswami Newbie

                I think , the problem is solved. There were two copies of the same Servlet classes in the JBoss jar file and the Tomcat war file. I do not always update the JBoss jar file as that requires a restart (hot deploy is broken in JBoss EJB). The Tomcat war file can be hot deployed. Unfortunately, Tomcat picks up the Servlet class from the EJB jar file rather than the Tomcat war file - I guess that is the price paid for using the same JVM. Although I think it can be corrected.