fixed typo of language

git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@992 50f2f4bb-b051-0410-bef5-90022cba6387

spring-framework-reference/src/cci.xml

@@ -432,7 +432,7 @@
       property must be directly specified on the <classname>CciTemplate</classname>.
       This could be done in the application code like so:</para>
 
-      <programlisting langauge="java"><![CDATA[cciTemplate.setOutputRecordCreator(new EciOutputRecordCreator());]]></programlisting>
+      <programlisting language="java"><![CDATA[cciTemplate.setOutputRecordCreator(new EciOutputRecordCreator());]]></programlisting>
 
       <para>Or (recommended) in the Spring configuration, if the <classname>CciTemplate</classname>
       is configured as a dedicated bean instance:</para>
@@ -628,7 +628,7 @@
       <interfacename>InteractionSpec</interfacename> must be done to specify which CICS
       program to access and how to interact with it.</para>
 
-      <programlisting langauge="java"><![CDATA[ECIInteractionSpec interactionSpec = new ECIInteractionSpec();
+      <programlisting language="java"><![CDATA[ECIInteractionSpec interactionSpec = new ECIInteractionSpec();
 interactionSpec.setFunctionName("MYPROG");
 interactionSpec.setInteractionVerb(ECIInteractionSpec.SYNC_SEND_RECEIVE);]]></programlisting>
 
@@ -808,7 +808,7 @@ interactionSpec.setInteractionVerb(ECIInteractionSpec.SYNC_SEND_RECEIVE);]]></pr
 			The following constructor must be used to instantiate an operation
       object with a specific <interfacename>InteractionSpec</interfacename>:</para>
 
-      <programlisting langauge="java"><![CDATA[InteractionSpec spec = ...;
+      <programlisting language="java"><![CDATA[InteractionSpec spec = ...;
 MyMappingRecordOperation eisOperation = new MyMappingRecordOperation(getConnectionFactory(), spec);
 ...]]></programlisting>
     </section>

spring-framework-reference/src/ejb.xml

@@ -88,7 +88,7 @@
 				EJB-specific business methods interface. Let’s call this business
 				methods interface <classname>MyComponent</classname>.
 			</para>
-			<programlisting langauge="java"><![CDATA[public interface MyComponent {
+			<programlisting language="java"><![CDATA[public interface MyComponent {
     ...
 }]]></programlisting>
 			<para>
@@ -105,7 +105,7 @@
 				on the controller. This will save the reference as an instance variable in the
 				controller:
 			</para>
-			<programlisting langauge="java"><![CDATA[private MyComponent myComponent;
+			<programlisting language="java"><![CDATA[private MyComponent myComponent;
 
 public void setMyComponent(MyComponent myComponent) {
     this.myComponent = myComponent;
@@ -351,7 +351,7 @@ public void setMyComponent(MyComponent myComponent) {
         shared container to be used by multiple EJBs or other clients. Doing this is relatively
         simple, by adding code similar to this to the EJB:
       </para>
-      <programlisting langauge="java"><![CDATA[   /**
+      <programlisting language="java"><![CDATA[   /**
     * Override default BeanFactoryLocator implementation
     * @see javax.ejb.SessionBean#setSessionContext(javax.ejb.SessionContext)
     */
@@ -395,7 +395,7 @@ public void setMyComponent(MyComponent myComponent) {
         in the EJB component class, or through an <literal>interceptor-binding</literal>
         XML element in the EJB deployment descriptor.
       </para>
-      <programlisting langauge="java"><![CDATA[@Stateless
+      <programlisting language="java"><![CDATA[@Stateless
 @Interceptors(SpringBeanAutowiringInterceptor.class)
 public class MyFacadeEJB implements MyFacadeLocal {
 

spring-framework-reference/src/jms.xml

@@ -350,7 +350,7 @@
     default destination. Here is an example that sends a message to a queue
     using the 1.0.2 implementation.</para>
 
-    <programlisting langauge="java"><![CDATA[import javax.jms.ConnectionFactory;
+    <programlisting language="java"><![CDATA[import javax.jms.ConnectionFactory;
 import javax.jms.JMSException;
 import javax.jms.Message;
 import javax.jms.Queue;
@@ -448,7 +448,7 @@ public class JmsQueueSender {
       example below demonstrates how to modify a message header and a property after
       a <interfacename>java.util.Map</interfacename> is converted to a message.</para>
 
-      <programlisting langauge="java"><![CDATA[public void sendWithConversion() {
+      <programlisting language="java"><![CDATA[public void sendWithConversion() {
     Map map = new HashMap();
     map.put("Name", "Mark");
     map.put("Age", new Integer(47));
@@ -520,7 +520,7 @@ public class JmsQueueSender {
   		receiving messages on multiple threads, it is important to ensure that your
   		implementation is thread-safe.</para>
 		<para>Below is a simple implementation of an MDP:</para>
-		<programlisting langauge="java"><![CDATA[import javax.jms.JMSException;
+		<programlisting language="java"><![CDATA[import javax.jms.JMSException;
 import javax.jms.Message;
 import javax.jms.MessageListener;
 import javax.jms.TextMessage;
@@ -546,7 +546,7 @@ public class ExampleListener implements MessageListener {
 		<para>Find below an example of how to define and configure one of the message listener
 		containers that ships with Spring (in this case the 
 		<classname>DefaultMessageListenerContainer</classname>).</para>
-		<programlisting langauge="xml"><lineannotation>&lt;!-- this is the Message Driven POJO (MDP) --&gt;</lineannotation>
+		<programlisting language="xml"><lineannotation>&lt;!-- this is the Message Driven POJO (MDP) --&gt;</lineannotation>
 <![CDATA[<bean id="messageListener" class="jmsexample.ExampleListener" />
 
 ]]><lineannotation>&lt;!-- and this is the message listener container --&gt;</lineannotation><![CDATA[
@@ -566,7 +566,7 @@ public class ExampleListener implements MessageListener {
   	    <interfacename>MessageListener</interfacename> interface, but also provides
   	    the message handling method with access to the JMS <interfacename>Session</interfacename>
   	    from which the <interfacename>Message</interfacename> was received.</para>
-  	    <programlisting langauge="java"><![CDATA[package org.springframework.jms.listener;
+  	    <programlisting language="java"><![CDATA[package org.springframework.jms.listener;
 
 public interface SessionAwareMessageListener {
 
@@ -609,7 +609,7 @@ public interface SessionAwareMessageListener {
         Notice also how the various message handling methods are strongly typed according to
         the <emphasis>contents</emphasis> of the various <interfacename>Message</interfacename>
         types that they can receive and handle.</para>
-        <programlisting langauge="java"><![CDATA[public interface MessageDelegate {
+        <programlisting language="java"><![CDATA[public interface MessageDelegate {
 
     void handleMessage(String message);
 
@@ -619,14 +619,14 @@ public interface SessionAwareMessageListener {
 
     void handleMessage(Serializable message);
 }]]></programlisting>
-        <programlisting langauge="java"><![CDATA[public class DefaultMessageDelegate implements MessageDelegate {
+        <programlisting language="java"><![CDATA[public class DefaultMessageDelegate implements MessageDelegate {
     ]]><lineannotation>// implementation elided for clarity...</lineannotation><![CDATA[
 }]]></programlisting>
         <para>In particular, note how the above implementation of the <interfacename>MessageDelegate</interfacename>
         interface (the above <classname>DefaultMessageDelegate</classname> class) has
         <emphasis>no</emphasis> JMS dependencies at all. It truly is a POJO that we will
         make into an MDP via the following configuration.</para>
-		<programlisting langauge="xml"><lineannotation>&lt;!-- this is the Message Driven POJO (MDP) --&gt;</lineannotation>
+		<programlisting language="xml"><lineannotation>&lt;!-- this is the Message Driven POJO (MDP) --&gt;</lineannotation>
 <emphasis role="bold"><![CDATA[<bean id="messageListener" class="org.springframework.jms.listener.adapter.MessageListenerAdapter">
     <constructor-arg>
         <bean class="jmsexample.DefaultMessageDelegate"/>
@@ -646,16 +646,16 @@ public interface SessionAwareMessageListener {
         <literal>'handleMessage'</literal>), but it is configurable (as you will see below).
         Notice also how the <literal>'receive(..)'</literal> method is strongly typed to
         receive and respond only to JMS <interfacename>TextMessage</interfacename> messages.</para>
-        <programlisting langauge="java"><![CDATA[public interface TextMessageDelegate {
+        <programlisting language="java"><![CDATA[public interface TextMessageDelegate {
 
     void receive(TextMessage message);
 }]]></programlisting>
-        <programlisting langauge="java"><![CDATA[public class DefaultTextMessageDelegate implements TextMessageDelegate {
+        <programlisting language="java"><![CDATA[public class DefaultTextMessageDelegate implements TextMessageDelegate {
     ]]><lineannotation>// implementation elided for clarity...</lineannotation><![CDATA[
 }]]></programlisting>
         <para>The configuration of the attendant <classname>MessageListenerAdapter</classname> would
         look like this:</para>
-        <programlisting langauge="xml"><![CDATA[<bean id="messageListener" class="org.springframework.jms.listener.adapter.MessageListenerAdapter">
+        <programlisting language="xml"><![CDATA[<bean id="messageListener" class="org.springframework.jms.listener.adapter.MessageListenerAdapter">
     <constructor-arg>
         <bean class="jmsexample.DefaultTextMessageDelegate"/>
     </constructor-arg>
@@ -673,12 +673,12 @@ public interface SessionAwareMessageListener {
         class is the ability to automatically send back a response <interfacename>Message</interfacename>
         if a handler method returns a non-void value.
         Consider the interface and class:</para>
-        <programlisting langauge="java"><![CDATA[public interface ResponsiveTextMessageDelegate {
+        <programlisting language="java"><![CDATA[public interface ResponsiveTextMessageDelegate {
 
     ]]><lineannotation><emphasis role="bold">// notice the return type...</emphasis></lineannotation><![CDATA[
     String receive(TextMessage message);
 }]]></programlisting>
-        <programlisting langauge="java"><![CDATA[public class DefaultResponsiveTextMessageDelegate implements ResponsiveTextMessageDelegate {
+        <programlisting language="java"><![CDATA[public class DefaultResponsiveTextMessageDelegate implements ResponsiveTextMessageDelegate {
     ]]><lineannotation>// implementation elided for clarity...</lineannotation><![CDATA[
 }]]></programlisting>
         <para>If the above <classname>DefaultResponsiveTextMessageDelegate</classname> 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.</para>
 
-			<programlisting langauge="xml"><![CDATA[<bean id="jmsContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer">
+			<programlisting language="xml"><![CDATA[<bean id="jmsContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer">
     <property name="connectionFactory" ref="connectionFactory"/>
     <property name="destination" ref="destination"/>
     <property name="messageListener" ref="messageListener"/>
@@ -736,7 +736,7 @@ public interface SessionAwareMessageListener {
 			part of the same transaction (with unified commit semantics,
 			at the expense of XA transaction log overhead).</para>
 
-  		<programlisting langauge="xml"><![CDATA[<bean id="transactionManager" class="org.springframework.transaction.jta.JtaTransactionManager"/>
+  		<programlisting language="xml"><![CDATA[<bean id="transactionManager" class="org.springframework.transaction.jta.JtaTransactionManager"/>
 ]]></programlisting>
 
 			<para>Then you just need to add it to our earlier container configuration. The

spring-framework-reference/src/mail.xml

@@ -59,7 +59,7 @@
 		
 		<section id="mail-usage-simple">
 			<title>Basic <interfacename>MailSender</interfacename> and <classname>SimpleMailMessage</classname> usage</title>
-			<programlisting langauge="java"><![CDATA[import org.springframework.mail.MailException;
+			<programlisting language="java"><![CDATA[import org.springframework.mail.MailException;
 import org.springframework.mail.MailSender;
 import org.springframework.mail.SimpleMailMessage;
 
@@ -101,7 +101,7 @@ public class SimpleOrderManager implements OrderManager {
 }]]></programlisting>
     
 			<para>Find below the bean definitions for the above code:</para>
-    		<programlisting langauge="xml"><![CDATA[<bean id="mailSender" class="org.springframework.mail.javamail.JavaMailSenderImpl">
+    		<programlisting language="xml"><![CDATA[<bean id="mailSender" class="org.springframework.mail.javamail.JavaMailSenderImpl">
   <property name="host" value="mail.mycompany.com"/>
 </bean>
 
@@ -126,7 +126,7 @@ public class SimpleOrderManager implements OrderManager {
 			<interfacename>JavaMailSender</interfacename> so that we are able to use the JavaMail
 			<classname>MimeMessage</classname> class:</para>
 			
-			<programlisting langauge="java"><![CDATA[import javax.mail.Message;
+			<programlisting language="java"><![CDATA[import javax.mail.Message;
 import javax.mail.MessagingException;
 import javax.mail.internet.InternetAddress;
 import javax.mail.internet.MimeMessage;
@@ -199,7 +199,7 @@ public class SimpleOrderManager implements OrderManager {
 		which shields you from having to use the verbose JavaMail API. Using
 		the <classname>MimeMessageHelper</classname> it is pretty easy to
 		create a <classname>MimeMessage</classname>:</para>
-		<programlisting langauge="java"><lineannotation>// of course you would use DI in any real-world cases</lineannotation><![CDATA[
+		<programlisting language="java"><lineannotation>// of course you would use DI in any real-world cases</lineannotation><![CDATA[
 JavaMailSenderImpl sender = new JavaMailSenderImpl();
 sender.setHost("mail.host.com");
 
@@ -220,7 +220,7 @@ sender.send(message);]]></programlisting>
 				<para>The following example shows you how to use the
 				<classname>MimeMessageHelper</classname> to send an email along with a
 				single JPEG image attachment.</para>
-				<programlisting langauge="java"><![CDATA[JavaMailSenderImpl sender = new JavaMailSenderImpl();
+				<programlisting language="java"><![CDATA[JavaMailSenderImpl sender = new JavaMailSenderImpl();
 sender.setHost("mail.host.com");
 
 MimeMessage message = sender.createMimeMessage();
@@ -242,7 +242,7 @@ sender.send(message);]]></programlisting>
 				<para>The following example shows you how to use the
 				<classname>MimeMessageHelper</classname> to send an email along with an
 				inline image.</para>
-				<programlisting langauge="java"><![CDATA[JavaMailSenderImpl sender = new JavaMailSenderImpl();
+				<programlisting language="java"><![CDATA[JavaMailSenderImpl sender = new JavaMailSenderImpl();
 sender.setHost("mail.host.com");
 
 MimeMessage message = sender.createMimeMessage();
@@ -309,7 +309,7 @@ sender.send(message);]]></programlisting>
 				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.</para>
-				<programlisting langauge="xml"><lineannotation># in the <literal>com/foo/package</literal></lineannotation><![CDATA[
+				<programlisting language="xml"><lineannotation># in the <literal>com/foo/package</literal></lineannotation><![CDATA[
 <html>
 <body>
 <h3>Hi ${user.userName}, welcome to the Chipping Sodbury On-the-Hill message boards!</h3>
@@ -323,7 +323,7 @@ sender.send(message);]]></programlisting>
 				<para>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).</para>
-				<programlisting langauge="java"><![CDATA[package com.foo;
+				<programlisting language="java"><![CDATA[package com.foo;
 
 import org.apache.velocity.app.VelocityEngine;
 import org.springframework.mail.javamail.JavaMailSender;

spring-framework-reference/src/remoting.xml

@@ -404,7 +404,7 @@ public class AccountServiceImpl implements AccountService {
       <interfacename>AccountService</interfacename> we extend Spring's
       <classname>ServletEndpointSupport</classname> class and implement our business
       logic here, usually delegating the call to the business layer.</para>
-      <programlisting langauge="java"><lineannotation>/**
+      <programlisting language="java"><lineannotation>/**
  * 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 <literal>@Autowired</literal>
       annotation for expressing such dependencies on Spring-managed beans.</para>
-      <programlisting langauge="java"><lineannotation>/**
+      <programlisting language="java"><lineannotation>/**
  * 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 <literal>@Autowired</literal>
 			configuration annotation still being honored:</para>
-      <programlisting langauge="java"><![CDATA[@WebService(serviceName="AccountService")
+      <programlisting language="java"><![CDATA[@WebService(serviceName="AccountService")
 public class AccountServiceEndpoint {
 
     @Autowired
@@ -828,14 +828,14 @@ public class AccountServiceEndpoint {
     <emphasis>same non-transactional</emphasis> <interfacename>Session</interfacename>, and as
     such throughput will be very implementation dependent.</para>
     <para>The following interface is used on both the server and the client side.</para>
-    <programlisting langauge="java"><![CDATA[package com.foo;
+    <programlisting language="java"><![CDATA[package com.foo;
 
 public interface CheckingAccountService {
 
     public void cancelAccount(Long accountId);
 }]]></programlisting>
     <para>The following simple implementation of the above interface is used on the server-side.</para>
-    <programlisting langauge="java"><![CDATA[package com.foo;
+    <programlisting language="java"><![CDATA[package com.foo;
 
 public class SimpleCheckingAccountService implements CheckingAccountService {
 
@@ -887,7 +887,7 @@ public class SimpleCheckingAccountService implements CheckingAccountService {
    </bean>
 
 </beans>]]></programlisting>
-      <programlisting langauge="java"><![CDATA[package com.foo;
+      <programlisting language="java"><![CDATA[package com.foo;
 
 import org.springframework.context.support.ClassPathXmlApplicationContext;
 
@@ -920,7 +920,7 @@ public class Server {
     </bean>
 
 </beans>]]></programlisting>
-      <programlisting langauge="java"><![CDATA[package com.foo;
+      <programlisting language="java"><![CDATA[package com.foo;
 
 import org.springframework.context.ApplicationContext;
 import org.springframework.context.support.ClassPathXmlApplicationContext;

spring-framework-reference/src/scheduling.xml

@@ -33,7 +33,7 @@
 			that makes the <classname>JobDetail</classname> more of an actual JavaBean
 			with sensible defaults. Let's have a look at an example:
 			</para>
-			<programlisting langauge="xml"><![CDATA[
+			<programlisting language="xml"><![CDATA[
 <bean name="exampleJob" class="org.springframework.scheduling.quartz.JobDetailBean">
   <property name="jobClass" value="example.ExampleJob" />
   <property name="jobDataAsMap">
@@ -93,7 +93,7 @@ public class ExampleJob extends QuartzJobBean {
   }
 }]]></programlisting>
 
-			<programlisting langauge="xml"><![CDATA[
+			<programlisting language="xml"><![CDATA[
 <bean id="exampleBusinessObject" class="examples.ExampleBusinessObject"/>]]></programlisting>
 			<para>Using the <classname>MethodInvokingJobDetailFactoryBean</classname>, you don't need to
 			create one-line jobs that just invoke a method, and you only need to create the actual