Why not ? ;-)
My understanding of JAX-RPC / JAXM is those API provides an easy way to send/receive SOAP requests.
So what does Axis provide ?
I guess as the acronym stands for "Apache Extensible Interaction system"...Axis provides a open and pluggable architecture !!
Some interesting features :
Chaining handlers to do additional processing either before or after the web service is invoked....
Develop your own Transport listener....
herve
*********************************
Herve Attia
Cell (650) 922-1973
Home (650) 992-3997
http://www.chez.com/attia/resume/
>From: "Stan Jordan" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: why Axis?
>Date: Wed, 20 Mar 2002 15:43:57 -0700
>
>Every time I pick up a magazine, I see an article advising Java programmers
>to build Web Services via JAX-RPC and JAXM APIs. The articles are complete
>with lotsa examples (but do not mention Axis).
>
>Where does Axis fit into this picture? I don't want to sound rude, but why
>would I program with Axis, rather than using the JAX-RPC and JAXM APIs?
>
>I am feeling a bit confused, and would appreciate some comments on "Where
>are we going with Axis?" Er, uh, "What is the plan?" If you could
>speculate beyond JAX-RPC and JAXM (to say, JAXB) that would be very cool.
>Thanks.
>Stan
>
>
Send and receive Hotmail on your mobile device: Click Here
