This is a good thread. +1 for Oliver's comments. In particular, the "extensible" nature of AXIS might very well make it the default Container for Web Services for a lot of Web services products built on top of it. I wouldnt be surprised if the next breed of WS companies take AXIS as the base and build on top of it.
Continuing in the same thread: Currently we have AXIS following the JAX-RPC spec. Are there plans for incorporating JAX-M ? I might be a little off-target here and forgive me, but if AXIS had to provide a reference implementation for JAX-*, how significant is that going to be? Romin. P.S: The "Sun" will see the light of the day. -----Original Message----- From: Oliver Suciu [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 28, 2002 4:47 PM To: [EMAIL PROTECTED] Subject: Re: Sun vs Axis? Quite the opposite -- it rather seems that Axis is emerging as the standard Java web service container, with support for Sun's JAX-RPC API. To me, it seems more like Axis is starting to become to web services (and JAX-RPC) what Tomcat is today for JSP & servlets -- the reference implementation. Somebody correct me if I'm wrong, please... -- Oliver Stan Jordan wrote: > > Axis and Sun seem to be going in different directions, seems to me, when it > comes to Web Services. A Web Service developer must choose one or the > other. I hate to see the Java world bifurcate like this. (I guess Sun > prolly has a speech somewhere called, "The Evil Axis") > Comments?
