@@ -271,7 +271,7 @@ In the newly created application context called `remoting-servlet.xml`, we'll cr
271271Now we're ready to link in the service at the client. No explicit handler mapping is
272272specified, mapping request URLs onto services, so `BeanNameUrlHandlerMapping` will be
273273used: Hence, the service will be exported at the URL indicated through its bean name
274- within the containing `DispatcherServlet`'s mapping (as defined above):
274+ within the containing `` DispatcherServlet` `'s mapping (as defined above):
275275`'http://HOST:8080/remoting/AccountService'`.
276276
277277Alternatively, create a `HessianServiceExporter` in your root application context (e.g.
@@ -425,7 +425,7 @@ dispatcher's application context:
425425 </bean>
426426----
427427
428- Such an exporter definition will be exposed through the `DispatcherServlet`'s standard
428+ Such an exporter definition will be exposed through the `` DispatcherServlet` `'s standard
429429mapping facilities, as explained in the section on Hessian.
430430
431431Alternatively, create an `HttpInvokerServiceExporter` in your root application context
@@ -1801,7 +1801,7 @@ synchronous receive calls is set using the property `setReceiveTimeout`.
18011801
18021802Some JMS providers allow the setting of default QOS values administratively through the
18031803configuration of the `ConnectionFactory`. This has the effect that a call to
1804- `MessageProducer`'s send method `send(Destination destination, Message message)` will
1804+ `` MessageProducer` `'s send method `send(Destination destination, Message message)` will
18051805use different QOS default values than those specified in the JMS specification. In order
18061806to provide consistent management of QOS values, the `JmsTemplate` must therefore be
18071807specifically enabled to use its own QOS values by setting the boolean property
@@ -2583,7 +2583,7 @@ Spring also provides a generic JCA message endpoint manager which is not tied to
25832583for using any message listener type (e.g. a CCI MessageListener) and any
25842584provider-specific ActivationSpec object. Check out your JCA provider's documentation to
25852585find out about the actual capabilities of your connector, and consult
2586- `GenericMessageEndpointManager`'s javadoc for the Spring-specific configuration details.
2586+ `` GenericMessageEndpointManager` `'s javadoc for the Spring-specific configuration details.
25872587
25882588[NOTE]
25892589====
@@ -3296,7 +3296,7 @@ a container that does not provide an `MBeanServer`. To address this you can crea
32963296`MBeanServer` instance declaratively by adding an instance of the
32973297`org.springframework.jmx.support.MBeanServerFactoryBean` class to your configuration.
32983298You can also ensure that a specific `MBeanServer` is used by setting the value of the
3299- `MBeanExporter`'s `server` property to the `MBeanServer` value returned by an
3299+ `` MBeanExporter` `'s `server` property to the `MBeanServer` value returned by an
33003300`MBeanServerFactoryBean`; for example:
33013301
33023302[source,xml,indent=0]
0 commit comments