RE: url-pattern not working with AxisServlet
That would be a correct. :) Perhaps an interesting annotation in the Axis 2 documentation as I am sure we are not the only ones using the connector. Straight forward once detected, but with all the setup that goes on introducting a new SOAP stack to a legacy development environment in can be overlooked. Case in point. Kurt -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Monday, May 05, 2008 11:22 PM To: Tomcat Users List Subject: Re: url-pattern not working with AxisServlet -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt, Kurt Kavanaugh wrote: | Not seeing the AxisServlet being invoked for /services/* url-pattern... [snip] | servlet-mapping | servlet-nameAxisServlet/servlet-name | url-pattern/services/*/url-pattern | /servlet-mapping [snip] | Apache [httpd] access INFO | | 127.0.0.1 - - [05/May/2008:12:05:30 -0400] GET /services/TestService | HTTP/1.1 404 306 404, eh? | Note there is no corresponding entry in the TOMCAT access log. No corresponding Tomcat access log entry, eh? | http://localhost//test/foo.do?SERIALNUMBER=XXXSTATUS=2 | the appropriate struts action gets called... however If I do this Other URLs work, eh? Sounds like you are missing a JkMount /services/* myWorker in your Apache httpd config file. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgfzvIACgkQ9CaO5/Lv0PBM0QCgqzbtnTkMl7HyPSdtZNhcRRU7 QBcAn1KulzOgCD0iisSLtwLcjsfaOD2D =yqJ/ -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: url-pattern not working with AxisServlet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt, Kurt Kavanaugh wrote: | That would be a correct. :) Perhaps an interesting annotation in the | Axis 2 documentation as I am sure we are not the only ones using the | connector. | | Straight forward once detected, but with all the setup that goes on | introducting a new SOAP stack to a legacy development environment in can | be overlooked. Case in point. I disagree that Axis should document this requirement. Axis has no requirements necessitating the use of Apache httpd. If your own environment has such requirements, it is up to you to appropriately configure it. There is plenty of documentation on using mod_jk to connect httpd to Tomcat. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkggrJoACgkQ9CaO5/Lv0PApfQCePT7N9MEscpnbLGyeqdHaDYPS ir4AoLUDqCheYCZR8JIXl3mlAkLLf6dq =jG9A -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: url-pattern not working with AxisServlet
Respectfully disagree Then why document Tomcat/Axis? Where is the line drawn? Axis has no business level requirements to run in a given container technology. Or do they? If a given set of elements, Apache,connector,Tomcat make up a common model of deployment why not facilitate? Anyway just an opinion, as stated I take full blame for not picking this up earlier. However, documentation is good. I see no downside, other than the time it takes to do so, and time is everything... :) Kurt -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 06, 2008 3:08 PM To: Tomcat Users List Subject: Re: url-pattern not working with AxisServlet -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt, Kurt Kavanaugh wrote: | That would be a correct. :) Perhaps an interesting annotation in the | Axis 2 documentation as I am sure we are not the only ones using the | connector. | | Straight forward once detected, but with all the setup that goes on | introducting a new SOAP stack to a legacy development environment in can | be overlooked. Case in point. I disagree that Axis should document this requirement. Axis has no requirements necessitating the use of Apache httpd. If your own environment has such requirements, it is up to you to appropriately configure it. There is plenty of documentation on using mod_jk to connect httpd to Tomcat. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkggrJoACgkQ9CaO5/Lv0PApfQCePT7N9MEscpnbLGyeqdHaDYPS ir4AoLUDqCheYCZR8JIXl3mlAkLLf6dq =jG9A -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: url-pattern not working with AxisServlet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt, Kurt Kavanaugh wrote: | Then why document Tomcat/Axis? Because Axis needs to be installed on a Java application server. Tomcat is a free one (and also under the Apache umbrella), so they go out of their way to tell you how to get it going. Apache httpd has nothing to do with it. | Where is the line drawn? Axis has no | business level requirements to run in a given container technology. Or | do they? Only that it supports a certain servlet specification (probably). The ASF is not known for giving free advertising to commercial containers. I checked, and there are no installation instructions for any container. There are only two gotchas listed on their website: one for Tomcat 4.x with Java 1.4 and one for weblogic. | If a given set of elements, Apache,connector,Tomcat make up a common | model of deployment why not facilitate? For the most part, that model is falling out of favor. | However, documentation is good. Fair enough. My opinion is irrelevant, anyway, as I am not a committer on the Asix project and have no part of any decision to update their documentation. Feel free to petition them to update their documentation. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgg0ZcACgkQ9CaO5/Lv0PAUbACgkJ4LJttBoEl+X6G+BnAlHSca CqAAoIlRFD7dm2gg7jm+Zk1d1QgajJQP =PpYK -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: url-pattern not working with AxisServlet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt, Kurt Kavanaugh wrote: | Not seeing the AxisServlet being invoked for /services/* url-pattern... [snip] | servlet-mapping | servlet-nameAxisServlet/servlet-name | url-pattern/services/*/url-pattern | /servlet-mapping [snip] | Apache [httpd] access INFO | | 127.0.0.1 - - [05/May/2008:12:05:30 -0400] GET /services/TestService | HTTP/1.1 404 306 404, eh? | Note there is no corresponding entry in the TOMCAT access log. No corresponding Tomcat access log entry, eh? | http://localhost//test/foo.do?SERIALNUMBER=XXXSTATUS=2 | the appropriate struts action gets called... however If I do this Other URLs work, eh? Sounds like you are missing a JkMount /services/* myWorker in your Apache httpd config file. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgfzvIACgkQ9CaO5/Lv0PBM0QCgqzbtnTkMl7HyPSdtZNhcRRU7 QBcAn1KulzOgCD0iisSLtwLcjsfaOD2D =yqJ/ -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
