Axis vs servlet, do it yourself

[David Thielen]

Hi;   I have a question about taking 3 different approaches to providing my program as a web service: Use axis Write a servlet and read/write the complete SOAP message Sit on a port of my own and and handle the http socket read/writes.   My question is what are the disadvantages as you move down the line.   Going from axis to servlet the only thing I can think of is you lose the upcoming xml security stuff that will be coming out in the next year. Is there any other downside? Goin the servlet route would definitely be faster. (No disrespect to the Axis team as it is a large product but I am going on my 10th day of trying to get a web service that C# can access too with no luck so the servlet route is less work.)   Going from servlet to my own server then I lose sharing the same port (not a biggie), not being able to be on a specific port like port 80 if it’s used by the application server (this could be big), and possibly better handling of very high traffic (although I’ve written some high traffic socket code so I’m not too worried about that).   Am I missing anything? Because time-wise I think doing it myself will be a lot faster. (I have to admit .net is wonderful in this respect – maybe 20 seconds to create the service and 1 minute to create the client.) So if there is no significant downside, I think I’ll go the servlet or do it myself route. (And I would create a .net client to make sure I’m exposing everything and displaying the wsdl correctly.)   Thanks - dave