On 6/21/05, Richard Mixon (qwest) <[EMAIL PROTECTED]> wrote: > I think for most practical purposes Tomcat is an application server. > > What Tomcat does not have is a builtin Enterprise Java Beans container - > however Tomcat supports many other parts of the J2EE spec. > > Simply by the numbers, the vast majority of Java web applications do not > use EJBs - so Tomcat is just fine for most users. EJBs are not necessary > at all for building sophisticated and complex web applications. Tomcat > offers load balancing and clustering - which used to be only offered by > commercial application servers. > > That said, there are some advantages to EJBs that can make the > additional complexity worth it. For some enterprise situations, you may > want an application server that is fully compliant with the J2EE spec, > such as Jboss, WebSphere, BEA or one of the other commercial packages. >
But it is not providing any services like transaction service, messaging service, remoting. Without these how it can be considered as an application server ?. -- rgds Anto Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
