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! =)
You didn't mention anything about the implementations you're using so it's hard to say anything about them :)
I don't know if your benchmark is representative of anything, I'm not sure it allows to make any valid conclusion.
JAX-WS is supposed to perform better in general than JAX-RPC, see the already mentioned article .
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.
java.rmi.Remote
interface concept. And uses RemoteException
ie all remote methods in a service endpoint interface (SEI) throw the standard java.rmi.RemoteException
. JAX-RPC 2.0 was renamed JAX-WS 2.0 . @WebService
, @SOAPBinding
, @WebMethod
, @WebParam
, @WebServiceClient
and so on.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.