----- Original Message ----- From: "Gene Chuang" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 02, 2003 23:34 Subject: Re: Packaging Axis...
> > I will eventually be packing axis in my webapp as well for transportability across servlet containers, so thanks for the pointers! > This does bring up an issue that perhaps has been addressed on this board before: I'm assuming that most J2EE vendor implementation of Web services is done using the Servlet container as a "host", I'm wondering if there are talks or actions to integrate Java Web Services into the Web-app specs so that: > 1) a Web service can be deployed in web.xml just like a Servlet That would need changes to the servlet specs. Better to have a standard cross-implementation XML file for declaring soap services; web.xml is not the be-all and and end-all of XML declarations in an war file; all the struts stuff is separate for one, taglibs are (partly) another example. > 2) architectures like Axis that use chain of Handlers can reimplement this as Servlet Filters they are similar, but different. That is, they are both a chain, but with different messages coming in. Also servlet filters are tied to http, and SOAP isnt. > 3) Web service impl classes can be hot-redeployed like Servlets 1. Axis handles hot redeployed .jws files, I think, on a par with .jsp 2. I have never had a good experience with in-situ updates of live code in a war; it is always safer to restart the webapp. > Perhaps an intermediate step (since getting JCP specs to change takes time) would be for Tomcat to adopt Axis and ship it under one OOB package. This would still require vendor-specific deployment process, but at least its better than what it is right now, which is also vendor-specific but difficult to integrate OOB. This needs much more version sync than anyone is ready for. But if you want to work on it, feel free. Tomcat 5.0 is likely to have some SOAP support.
