File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Web Services and the fly likes Axis vs. JAX-RPC vs. Apache Soap Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Axis vs. JAX-RPC vs. Apache Soap" Watch "Axis vs. JAX-RPC vs. Apache Soap" New topic

Axis vs. JAX-RPC vs. Apache Soap

Peter Pascale

Joined: Jan 18, 2001
Posts: 17
I have a few questions about these technologies. Feel free to pipe up on any one you know something about.
It seems that each is an implementation tool for java web service development. I am charged with developing a somewhat simple web service client toolset for one of our applications. Essentially we will be doing RPC using SOAP (no fancy async calls, although complex types will be included as params and return types). The definition for the service we're interacting with will be pretty static - pretty stable WSDL. So I'm wondering?
1) Does Axis replace apache Soap in functionality? It seems that apache Soap is still relevant for simple RPC type usage. Although I like the axis framework for its handlers...
2) Has anyone seen REAL JAX-RPC examples outside of Sun's java web services tutorial? I've had no success running a simple JAX-RPC client against a web service implemented in GLUE at XMethods. I know the service is up, because my apache Soap client can hit it.
3) Any experience with either of these implementations?
I agree. Here's the link:
subject: Axis vs. JAX-RPC vs. Apache Soap
It's not a secret anymore!