@@ -16,28 +16,29 @@ a number of Java EE (and related) technologies.
16
16
17
17
18
18
[[remoting]]
19
- == Remoting and Web Services with Spring
19
+ == Remoting and Web Services
20
20
21
- Spring features integration classes for remoting support with various technologies.
21
+ Spring provides support for remoting with various technologies.
22
22
The remoting support eases the development of remote-enabled services, implemented
23
- by your usual POJOs. Currently, Spring supports the following remoting technologies:
23
+ via Java interfaces and objects as input and output. Currently, Spring supports the
24
+ following remoting technologies:
24
25
25
- * * Remote Method Invocation (RMI)* : Through the use of `RmiProxyFactoryBean` and
26
+ * <<remoting-rmi, Remote Method Invocation (RMI)>> : Through the use of `RmiProxyFactoryBean` and
26
27
`RmiServiceExporter`, Spring supports both traditional RMI (with `java.rmi.Remote`
27
28
interfaces and `java.rmi.RemoteException`) and transparent remoting through RMI
28
29
invokers (with any Java interface).
29
- * *Spring's HTTP invoker* : Spring provides a special remoting strategy that allows
30
+ * <<remoting-httpinvoker>> : Spring provides a special remoting strategy that allows
30
31
for Java serialization though HTTP, supporting any Java interface (as the RMI
31
32
invoker does). The corresponding support classes are `HttpInvokerProxyFactoryBean`
32
33
and `HttpInvokerServiceExporter`.
33
- * *Hessian* : By using Spring's `HessianProxyFactoryBean` and the
34
+ * <<remoting-caucho-protocols-hessian>> : By using Spring's `HessianProxyFactoryBean` and the
34
35
`HessianServiceExporter`, you can transparently expose your services through the
35
36
lightweight binary HTTP-based protocol provided by Caucho.
36
- * *JAX-WS* : Spring provides remoting support for web services through JAX-WS.
37
- * *JMS* : Remoting via JMS as the underlying protocol is supported through the
37
+ * <<remoting-web-services>> : Spring provides remoting support for web services through JAX-WS.
38
+ * <<remoting-jms>> : Remoting via JMS as the underlying protocol is supported through the
38
39
`JmsInvokerServiceExporter` and `JmsInvokerProxyFactoryBean` classes in the
39
40
`spring-jms` module.
40
- * *AMQP* : Remoting via AMQP as the underlying protocol is supported by the
41
+ * <<remoting-amqp>> : Remoting via AMQP as the underlying protocol is supported by the
41
42
separate Spring AMQP project.
42
43
43
44
While discussing the remoting capabilities of Spring, we use the following domain
@@ -94,7 +95,7 @@ the protocol.
94
95
95
96
96
97
[[remoting-rmi]]
97
- === Exposing Services by Using RMI
98
+ === RMI
98
99
99
100
By using Spring's support for RMI, you can transparently expose your services through the
100
101
RMI infrastructure. After having this set up, you basically have a configuration similar
@@ -200,7 +201,7 @@ and you can find more information about Hessian itself at https://www.caucho.com
200
201
201
202
202
203
[[remoting-caucho-protocols-hessian]]
203
- ==== Wiring up `DispatcherServlet` for Hessian
204
+ ==== Hessian
204
205
205
206
Hessian communicates through HTTP and does so by using a custom servlet. By using Spring's
206
207
`DispatcherServlet` principles (see <<webmvc.adoc#mvc-servlet>>), we can wire up such a
@@ -346,7 +347,7 @@ at https://projects.spring.io/spring-security/.
346
347
347
348
348
349
[[remoting-httpinvoker]]
349
- === Exposing Services by Using HTTP Invokers
350
+ === Spring HTTP Invoker
350
351
351
352
As opposed to Hessian, Spring HTTP invokers are both lightweight protocols that use their own slim
352
353
serialization mechanisms and use the standard Java serialization
@@ -464,7 +465,7 @@ The following example shows how to do so:
464
465
465
466
466
467
[[remoting-web-services]]
467
- === Web Services
468
+ === Java Web Services
468
469
469
470
Spring provides full support for the standard Java web services APIs:
470
471
@@ -682,7 +683,7 @@ accordingly first. Check the JAX-WS documentation for details on those requireme
682
683
683
684
684
685
[[remoting-jms]]
685
- === Exposing Services through JMS
686
+ === JMS
686
687
687
688
You can also expose services transparently by using JMS as the underlying communication
688
689
protocol. The JMS remoting support in the Spring Framework is pretty basic. It sends
@@ -842,8 +843,9 @@ The following example defines beans that you can inject into other client-side o
842
843
843
844
[[remoting-amqp]]
844
845
=== AMQP
845
- See the {doc-spring-amqp}/html/_reference.html#remoting[Spring AMQP Reference Guide's
846
- 'Spring Remoting with AMQP' section] for more information.
846
+ Remoting via AMQP as the underlying protocol is supported in the Spring AMQP project.
847
+ For further details please visit the {doc-spring-amqp}/html/#remoting[Spring Remoting]
848
+ section of the Spring AMQP reference.
847
849
848
850
[[remoting-autodection-remote-interfaces]]
849
851
[NOTE]
@@ -925,7 +927,7 @@ major new features added going forward.
925
927
926
928
927
929
[[rest-resttemplate]]
928
- ==== Using `RestTemplate`
930
+ ==== `RestTemplate`
929
931
930
932
The `RestTemplate` provides a higher level API over HTTP client libraries. It makes it
931
933
easy to invoke REST endpoints in a single line. It exposes the following groups of
0 commit comments