JAX-WS vs. JAX-RPC

Question

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! =)

Answer 1

Here's an article that provides performance comparison between two methods.

Answer 2

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.