Skip to content

Commit 63bf1bf

Browse files
committed
Merge branch '5.1.x'
2 parents 5bb5b2b + 70be711 commit 63bf1bf

File tree

1 file changed

+19
-17
lines changed

1 file changed

+19
-17
lines changed

src/docs/asciidoc/integration.adoc

Lines changed: 19 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -16,28 +16,29 @@ a number of Java EE (and related) technologies.
1616

1717

1818
[[remoting]]
19-
== Remoting and Web Services with Spring
19+
== Remoting and Web Services
2020

21-
Spring features integration classes for remoting support with various technologies.
21+
Spring provides support for remoting with various technologies.
2222
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:
2425

25-
* *Remote Method Invocation (RMI)*: Through the use of `RmiProxyFactoryBean` and
26+
* <<remoting-rmi,Remote Method Invocation (RMI)>>: Through the use of `RmiProxyFactoryBean` and
2627
`RmiServiceExporter`, Spring supports both traditional RMI (with `java.rmi.Remote`
2728
interfaces and `java.rmi.RemoteException`) and transparent remoting through RMI
2829
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
3031
for Java serialization though HTTP, supporting any Java interface (as the RMI
3132
invoker does). The corresponding support classes are `HttpInvokerProxyFactoryBean`
3233
and `HttpInvokerServiceExporter`.
33-
* *Hessian*: By using Spring's `HessianProxyFactoryBean` and the
34+
* <<remoting-caucho-protocols-hessian>>: By using Spring's `HessianProxyFactoryBean` and the
3435
`HessianServiceExporter`, you can transparently expose your services through the
3536
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
3839
`JmsInvokerServiceExporter` and `JmsInvokerProxyFactoryBean` classes in the
3940
`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
4142
separate Spring AMQP project.
4243

4344
While discussing the remoting capabilities of Spring, we use the following domain
@@ -94,7 +95,7 @@ the protocol.
9495

9596

9697
[[remoting-rmi]]
97-
=== Exposing Services by Using RMI
98+
=== RMI
9899

99100
By using Spring's support for RMI, you can transparently expose your services through the
100101
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
200201

201202

202203
[[remoting-caucho-protocols-hessian]]
203-
==== Wiring up `DispatcherServlet` for Hessian
204+
==== Hessian
204205

205206
Hessian communicates through HTTP and does so by using a custom servlet. By using Spring's
206207
`DispatcherServlet` principles (see <<webmvc.adoc#mvc-servlet>>), we can wire up such a
@@ -346,7 +347,7 @@ at https://projects.spring.io/spring-security/.
346347

347348

348349
[[remoting-httpinvoker]]
349-
=== Exposing Services by Using HTTP Invokers
350+
=== Spring HTTP Invoker
350351

351352
As opposed to Hessian, Spring HTTP invokers are both lightweight protocols that use their own slim
352353
serialization mechanisms and use the standard Java serialization
@@ -464,7 +465,7 @@ The following example shows how to do so:
464465

465466

466467
[[remoting-web-services]]
467-
=== Web Services
468+
=== Java Web Services
468469

469470
Spring provides full support for the standard Java web services APIs:
470471

@@ -682,7 +683,7 @@ accordingly first. Check the JAX-WS documentation for details on those requireme
682683

683684

684685
[[remoting-jms]]
685-
=== Exposing Services through JMS
686+
=== JMS
686687

687688
You can also expose services transparently by using JMS as the underlying communication
688689
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
842843

843844
[[remoting-amqp]]
844845
=== 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.
847849

848850
[[remoting-autodection-remote-interfaces]]
849851
[NOTE]
@@ -925,7 +927,7 @@ major new features added going forward.
925927

926928

927929
[[rest-resttemplate]]
928-
==== Using `RestTemplate`
930+
==== `RestTemplate`
929931

930932
The `RestTemplate` provides a higher level API over HTTP client libraries. It makes it
931933
easy to invoke REST endpoints in a single line. It exposes the following groups of

0 commit comments

Comments
 (0)