Ahh, this seems like a good time for us to discuss SimpleAxisServer a bit. I'll also throw my ideas about stand-alone / embeddable Axis in as well.
It appears to me that the SimpleAxisServer is being used primarily for automated testing, as well as quick-and-dirty service deployment for some folks (again, I'm sure this is for testing). Now, in order to add support for testing the servlet-based GUI that I've been working on via SimpleAxisServer without requiring Axis to be deployed to a Tomcat/Websphere/etc server, I need to do one of the following: a) Add query string / parameter parsing and then manually drive my classes in a non-servlet manner behind the scenes. b) Evolve SimpleAxisServer into a basic-servlet container and then host AxisServlet as a servlet. c) Use a free, embeddable servlet container that already fits the bill. (Jetty?) My comments... a) This would be a one-off type of change that would only serve my purposes and would not necessarily be reusable in other contexts. Therefore, I'm leaning away from this method. b) This solution could be a Good Thing(tm) if the concensus is that we should grow SimpleAxisServer into NotSoSimpleAxisServer. What do you guys think? I'm ok with implementing a very basic container if need be, but this is not my preference. c) We could use an http server / servlet container that supports HTTP/HTTPS, MIME, as well as the Servlet API to provide a one-stop shop for serious testing and even small production deployments. Imagine if a user could simply download Axis and begin deploying WS's. I know, I know, most folks doing serious work will already have a server for deploying Axis, but I would argue that a large majority of newcomers would find this type of "single jar" solution attractive. The benefits of c) would be multi-faceted... * Automated testing could be taken up a notch for things like MIME & HTTPS support. * We could create an "Axis Server" distro that folks could use for actually deploying WS's. * We could create an "Embeddable Axis" distro that folks could use for trivially adding support for WS's, both client _and_ server-side into their existing, and future, applications. ----These last two could also help to get press/attention for the Axis project in general. Note: I'm already experienced with embedding Jetty (http://jetty.mortbay.com/) into our application server and would be glad to contribute the integration work to make this happen in Axis. FYI, Here's the high-level feature list for Jetty (from their website): * 100% Java Server * Open Source * HTTP Protocol 1.1 * Servlet API 2.3 * Java Server Pages 1.2 * SSL Support * Modular Architecture * Embeddable * Small & Efficient * Flexible Configuration * HTML Generation. * EJB & JMX Integration Also note that I'm not affiliated with Jetty in any way, shape or form. It's just a really great tool and seems to be appropriate for this type of thing, IMHO. Thanks for reading this far, please let me know what you think of these ideas. Am I way off base here? Alan -----Original Message----- From: Glen Daniels [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 2:50 PM To: '[EMAIL PROTECTED]' Subject: RE: cvs commit: xml-axis/java/samples/attachments EchoAttachment. java > Add a functional test for attachments but comment it out since > SimpleAxisServer doesn't support it. If we ever switch to > a real server (like Tomcat) ... ...or add MIME support to SimpleAxisServer.... --G
