Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

JAX-WS vs. JAX-RPC

Tags:

I wrote 2 webservices, one with Jax-WS and one with Jax-RPC. They just return a String.

I stress-tested both with jMeter and, strangely, thereby Jax-RPC was a bit faster.

When do I really profit of Jax-WS in aspects of performance (response time, CPU-time, heap)? How can I proof it?

thanks for your time! =)

like image 769
norminka Avatar asked Jul 22 '10 09:07

norminka


People also ask

What is the difference between JAX-RPC and JAX-WS?

JAX-WS and JAX-RPC are Java programming APIs that are used in the web service bindings, to create and consume SOAP messages. JAX-WS is the successor to JAX-RPC. This topic describes the similarities and differences between the two. Using the web service binding, you can specify that messages are processed by handlers.

What is JAX-RPC used for?

Java APIs for XML-based Remote Procedure Call ( JAX-RPC) help with Web service interoperability and accessibility by defining Java APIs that Java applications use to develop and access Web services.

Which SOAP bindings does JAX-RPC support?

JAX-RPC and JAX-WS both support SOAP 1.1. The default binding supported by JAX-WS is SOAP 1.1 over HTTP. But it can also support SOAP 1.2 binding over HTTP. As a Java programmer you might not encounter any difference between SOAP 1.1 and SOAP 1.2.

What is defined by JAX-RPC specification?

JAX-RPC is a specification that defines the Java APIs for making XML-based remote procedure calls (RPC). In particular, these APIs are used to invoke and get a response from a web service using SOAP 1.1, and XML-based protocol for exchange of information in a decentralized and distributed environment.


1 Answers

  1. You didn't mention anything about the implementations you're using so it's hard to say anything about them :)

  2. I don't know if your benchmark is representative of anything, I'm not sure it allows to make any valid conclusion.

  3. JAX-WS is supposed to perform better in general than JAX-RPC, see the already mentioned article.

  4. JAX-RPC is a dead standard that has been pruned in Java EE 6 (and might thus be removed from future versions). Reason for Pruning: JAX-RPC was an early attempt at modeling SOAP web services as RPC calls. Web services have since grown out of being an RPC model. The much more robust, feature-rich and popular JAX-WS API effectively supercedes JAX-RPC.

To summarize, I would definitely not base a new project on JAX-RPC.

like image 79
Pascal Thivent Avatar answered Oct 08 '22 07:10

Pascal Thivent