Geek asks and answers

Practical difference between JAX-RPC and JAX-WS vs JAX-RS

I know that a lot of documents are available on the web that mainly describe technical differences.

But I am interested to know what common use cases are, when you prefer one particular type over another, why?

Are these preferences as integration patterns / products support a certain type?

+3
source share
3 answers

Thanks for the answer. However, the practical difference in use and when to use what. Both JAX-WS and JAX-RS have standard implementations. I came up with the following differences:

RESTful services (most often web integration, mobile phone applications)

  • Integration over the Internet will be easy with REST. Popularly used with AJAX calls.
  • , SOAP- , .
  • - , .

JAX-WS JAX-RPC - SOAP. (- )

JAX-WS Java EE , .  - , SOAP, - , .  - -, , , .

+11

JAX-RPC . - Java.

JAX-WS SOAP - - ( )

JAX-RS REST - -

+7

@Arjan Tijms

JAX-WS Java 5.0, J2EE5.0 JAX-RPC J2EE 1.4 J2EE 5.0.

JAX-RPC , , , , javax.xml.soap.SOAPElement.

JAX-WS JAXB, promises XML, , XSD XSD, , XML .

Webservice , JAX-RPC, , , Jax-WS .

The common thing is that both are confusing when used with J2EE 5.0, JavaEE 6.x. Better Jax-RS or Jersey for new implementations and redesigns. or you can continue to work with JAX-RPC or JAX-WS.

JavaEE7.0 promises is a new easy, developer-friendly and tester approach for RESTful web services.

The Java XML Binding Architecture (JAXB) is an XML-to-Java binding technology that simplifies web service development by incorporating transformations between a schema and Java objects and between XML instance documents and Java object instances.

+1
source

More articles:


All Articles