From a4b1adbc60ece228b0aaf77320a6cfbac827cf0f Mon Sep 17 00:00:00 2001 From: Thomas Risberg Date: Tue, 14 Apr 2009 04:35:40 +0000 Subject: [PATCH] fixed typo of language --- spring-framework-reference/src/cci.xml | 6 ++-- spring-framework-reference/src/ejb.xml | 8 ++--- spring-framework-reference/src/jms.xml | 30 +++++++++---------- spring-framework-reference/src/mail.xml | 16 +++++----- spring-framework-reference/src/remoting.xml | 14 ++++----- spring-framework-reference/src/scheduling.xml | 4 +-- 6 files changed, 39 insertions(+), 39 deletions(-) diff --git a/spring-framework-reference/src/cci.xml b/spring-framework-reference/src/cci.xml index 94528573a00..a960eca3b20 100644 --- a/spring-framework-reference/src/cci.xml +++ b/spring-framework-reference/src/cci.xml @@ -432,7 +432,7 @@ property must be directly specified on the CciTemplate. This could be done in the application code like so: - + Or (recommended) in the Spring configuration, if the CciTemplate is configured as a dedicated bean instance: @@ -628,7 +628,7 @@ InteractionSpec must be done to specify which CICS program to access and how to interact with it. - @@ -808,7 +808,7 @@ interactionSpec.setInteractionVerb(ECIInteractionSpec.SYNC_SEND_RECEIVE);]]>InteractionSpec: - diff --git a/spring-framework-reference/src/ejb.xml b/spring-framework-reference/src/ejb.xml index f493c3080d6..061bea43beb 100644 --- a/spring-framework-reference/src/ejb.xml +++ b/spring-framework-reference/src/ejb.xml @@ -88,7 +88,7 @@ EJB-specific business methods interface. Let’s call this business methods interface MyComponent. - @@ -105,7 +105,7 @@ on the controller. This will save the reference as an instance variable in the controller: - - interceptor-binding XML element in the EJB deployment descriptor. - - java.util.Map is converted to a message. - Below is a simple implementation of an MDP: - Find below an example of how to define and configure one of the message listener containers that ships with Spring (in this case the DefaultMessageListenerContainer). - <!-- this is the Message Driven POJO (MDP) --> + <!-- this is the Message Driven POJO (MDP) --> ]]><!-- and this is the message listener container -->MessageListener interface, but also provides the message handling method with access to the JMS Session from which the Message was received. - contents of the various Message types that they can receive and handle. - - // implementation elided for clarity... In particular, note how the above implementation of the MessageDelegate interface (the above DefaultMessageDelegate class) has no JMS dependencies at all. It truly is a POJO that we will make into an MDP via the following configuration. - <!-- this is the Message Driven POJO (MDP) --> + <!-- this is the Message Driven POJO (MDP) --> @@ -646,16 +646,16 @@ public interface SessionAwareMessageListener { 'handleMessage'), but it is configurable (as you will see below). Notice also how the 'receive(..)' method is strongly typed to receive and respond only to JMS TextMessage messages. - - // implementation elided for clarity... The configuration of the attendant MessageListenerAdapter would look like this: - + @@ -673,12 +673,12 @@ public interface SessionAwareMessageListener { class is the ability to automatically send back a response Message if a handler method returns a non-void value. Consider the interface and class: - // notice the return type... - // implementation elided for clarity... If the above DefaultResponsiveTextMessageDelegate is used in @@ -714,7 +714,7 @@ public interface SessionAwareMessageListener { implementation, covering the case where database processing has committed but message processing failed to commit. - + @@ -736,7 +736,7 @@ public interface SessionAwareMessageListener { part of the same transaction (with unified commit semantics, at the expense of XA transaction log overhead). - + ]]> Then you just need to add it to our earlier container configuration. The diff --git a/spring-framework-reference/src/mail.xml b/spring-framework-reference/src/mail.xml index 44de512b52e..90e87175735 100644 --- a/spring-framework-reference/src/mail.xml +++ b/spring-framework-reference/src/mail.xml @@ -59,7 +59,7 @@
Basic <interfacename>MailSender</interfacename> and <classname>SimpleMailMessage</classname> usage - Find below the bean definitions for the above code: - + @@ -126,7 +126,7 @@ public class SimpleOrderManager implements OrderManager { JavaMailSender so that we are able to use the JavaMail MimeMessage class: - MimeMessageHelper it is pretty easy to create a MimeMessage: - // of course you would use DI in any real-world cases// of course you would use DI in any real-world cases The following example shows you how to use the MimeMessageHelper to send an email along with a single JPEG image attachment. - The following example shows you how to use the MimeMessageHelper to send an email along with an inline image. - template that this example will be using... as you can see it is HTML-based, and since it is plain text it can be created using your favorite HTML editor without recourse to having to know Java. - # in the com/foo/package# in the com/foo/package

Hi ${user.userName}, welcome to the Chipping Sodbury On-the-Hill message boards!

@@ -323,7 +323,7 @@ sender.send(message);]]> Find below some simple code and Spring XML configuration that makes use of the above Velocity template to create email content and send email(s). - AccountService we extend Spring's ServletEndpointSupport class and implement our business logic here, usually delegating the call to the business layer. - /** + /** * JAX-RPC compliant RemoteAccountService implementation that simply delegates * to the AccountService implementation in the root web application context. * @@ -615,7 +615,7 @@ public class AccountServiceEndpoint extends ServletEndpointSupport implements Re logic here, usually delegating the call to the business layer. We'll simply use Spring 2.5's @Autowired annotation for expressing such dependencies on Spring-managed beans. - /** + /** * JAX-WS compliant AccountService implementation that simply delegates * to the AccountService implementation in the root web application context. * @@ -684,7 +684,7 @@ public class AccountServiceEndpoint extends SpringBeanAutowiringSupport { This means that the endpoint implementation may look like as follows, without any superclass declared - and Spring's @Autowired configuration annotation still being honored: - same non-transactional Session, and as such throughput will be very implementation dependent. The following interface is used on both the server and the client side. - The following simple implementation of the above interface is used on the server-side. - ]]> - ]]> - JobDetail more of an actual JavaBean with sensible defaults. Let's have a look at an example: - @@ -93,7 +93,7 @@ public class ExampleJob extends QuartzJobBean { } }]]> - ]]> Using the MethodInvokingJobDetailFactoryBean, you don't need to create one-line jobs that just invoke a method, and you only need to create the actual