Excellent - thanks very much for this good info Paul.
Paul Fremantle wrote:
Demetris Partly this is historical... Axis1 originally had a single-threaded server built in for test purposes, which was not production ready. The SimpleHTTPServer that is built into Axis2 is much more robust and reasonable performant. In my understanding it is "good enough" for production usage, though perhaps not for really hard-core heavy-duty requirements. Its also very useful if you want to embed in an existing application (public void main()). However, Tomcat is definitely faster, so if performance is an issue, I'd go for Tomcat. Also Tomcat has a lot more resources on scaling, tuning, plus the native IO handlers etc. There is a third option which is the NIO HTTP transport that originated in Synapse. This is very efficient and scales to very large numbers of concurrent connections (>1000), and has been production tested in the Synapse community with very good results. Paul On Dec 23, 2007 6:26 AM, Demetris G <[EMAIL PROTECTED]> wrote:Hi all, there was a discussion once whether Axis2 should be run standalone for production software - or something of this nature. I know Axis2 can be a web services container (standalone) and can also be executed from within a servlet container. Can someone please shed some light on this again? Was it the use of the HTTP server? Thanks much --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
