-
1. Re: HTTP POST -solved (caused by broken hot deploy)
simperitog Dec 17, 2002 2:41 PM (in response to simperitog)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)
simperitog Dec 17, 2002 2:43 PM (in response to simperitog)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
simperitog Dec 17, 2002 2:44 PM (in response to simperitog)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
simperitog Dec 17, 2002 2:46 PM (in response to simperitog)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.