Consider how many people use Tomcat rather than a full J2EE server. Axis is the most popular web services platform for Tomcat. I just spoke with a client that uses Tomcat/Axis in production, and they have no interest in upgrading to a J2EE platform.
I, for one, really like the current focus of designing a light, fast, standalone Java SOAP engine with all the latest features. The industry needs one. At the same time, I think a plan to adopt Web Services Metadata (JSR-181) sooner rather than later is really important because it may impact some core design issues. Anne On 7/29/05, Venkat Reddy <[EMAIL PROTECTED]> wrote: > This got me thinking a bit, trying to envision major usage patterns > for Axis2 in near future. Currently we seem to be primarily targetting > a usecase where Axis2 is used as a standalone Java SOAP engine, that > is light and fast without the stuff like JAXRPC, and with all the good > stuff like stream parsing, Addressing, RM, asynchrony, MTOM, > modularity, pluggable databinding etc. > > I wonder how Axis2 would look like in a big enterprise picture, and > what could be possible scenarios for total solutions using Axis2. How > easy to embed it inside in a J2EE app server, whether it passes the WS > specific part of Sun's CTS for J2EE1.4, or if it can be managed / > controlled remotely, or does it fit into an IOC container, or can it > easily be carved into something like a GBean, and so on ...... > > - venkat > > > On 7/29/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > > See: > > http://jboss.org/jbossBlog/blog/tdiesler/?permalink=JBoss_web_service_stack_EA1_released.txt > > > > Sanjiva. > > > > >
