Add missing language attributes to programlisting tags for highlighting.

Author: tekul

docs/docs.gradle

@@ -1,4 +1,4 @@
-// Docbook and Javadoc building and uploading tasks
+    // Docbook and Javadoc building and uploading tasks
 apply plugin: 'base'
 
 task docs {
@@ -47,6 +47,12 @@ project('manual') {
     }
 }
 
+task reference (type: Copy) {
+    dependsOn 'manual:docbook'
+    destinationDir = buildDir
+    with(project('manual').spec)
+}
+
 task apidocs(type: Javadoc) {
     destinationDir = new File(buildDir, 'apidocs')
     title = "Spring Security $version API"

docs/faq/src/docbook/faq.xml

@@ -282,7 +282,7 @@
                 <answer><para>Make sure you have added the listener to your web.xml file. It is
                         essential to make sure that the Spring Security session registry is notified
                         when a session is destroyed. Without it, the session information will not be
-                        removed from the registry.</para><programlisting><![CDATA[
+                        removed from the registry.</para><programlisting language="xml"><![CDATA[
     <listener>
         <listener-class>org.springframework.security.ui.session.HttpSessionEventPublisher</listener-class>
     </listener> ]]>

docs/manual/src/docbook/anon-auth-provider.xml

@@ -54,7 +54,7 @@
             <classname>SecurityContextHolder</classname> if there is no existing
             <interfacename>Authentication</interfacename> held there. The definition of the filter
             and authentication provider appears as follows:</para>
-        <para> <programlisting>
+        <para> <programlisting language="xml">
 <![CDATA[
 <bean id="anonymousAuthFilter"
     class="org.springframework.security.web.authentication.AnonymousAuthenticationFilter">
@@ -89,7 +89,7 @@
             <literal>InMemoryDaoImpl</literal>'s <literal>userMap</literal> property.</para>
         <para>As explained earlier, the benefit of anonymous authentication is that all URI patterns
             can have security applied to them. For example:</para>
-        <para> <programlisting>
+        <para> <programlisting language="xml">
 <![CDATA[
 <bean id="filterSecurityInterceptor"
     class="org.springframework.security.web.access.intercept.FilterSecurityInterceptor">

docs/manual/src/docbook/appendix-db-schema.xml

@@ -136,7 +136,7 @@ create table acl_entry (
         <section>
         <title>PostgreSQL</title>
         <para>
-        <programlisting>create table acl_sid(
+        <programlisting language="ddl">create table acl_sid(
   id bigserial not null primary key,
   principal boolean not null,
   sid varchar(100) not null,

docs/manual/src/docbook/appendix-namespace.xml

@@ -602,7 +602,7 @@
                     <interfacename>AuthenticationProvider</interfacename> implementation (or want to
                     configure one of Spring Security's own implementations as a traditional bean for
                     some reason, then you can use the following syntax to add it to the internal
-                    <classname>ProviderManager</classname>'s list: <programlisting><![CDATA[
+                    <classname>ProviderManager</classname>'s list: <programlisting language="xml"><![CDATA[
   <security:authentication-manager>
     <security:authentication-provider ref="myAuthenticationProvider" />
   </security:authentication-manager>

docs/manual/src/docbook/authorization-common.xml

@@ -17,7 +17,7 @@
             <interfacename>AccessDecisionManager</interfacename>s when making authorization
             decisions.</para>
         <para><interfacename>GrantedAuthority</interfacename> is an interface with only one method:
-            <programlisting>
+            <programlisting language="java">
   String getAuthority();
     </programlisting> This method allows
             <interfacename>AccessDecisionManager</interfacename>s to obtain a precise
@@ -63,7 +63,7 @@
                 final access control decisions. The
                 <interfacename>AccessDecisionManager</interfacename> interface contains three
                 methods:
-                <programlisting>
+                <programlisting language="java">
  void decide(Authentication authentication, Object secureObject,
      Collection&lt;ConfigAttribute&gt; attrs) throws AccessDeniedException;
  boolean supports(ConfigAttribute attribute);
@@ -112,7 +112,7 @@
                 based on its assessment of the votes.</para>
             <para>The <interfacename>AccessDecisionVoter</interfacename> interface has three
                 methods:
-                <programlisting>
+                <programlisting language="java">
 int vote(Authentication authentication, Object object, Collection&lt;ConfigAttribute&gt; attrs);
 boolean supports(ConfigAttribute attribute);
 boolean supports(Class clazz);
@@ -243,15 +243,15 @@ boolean supports(Class clazz);
       <para>A common services layer method we've all written at one stage or another looks like
         this:</para>
       <para>
-        <programlisting>public Contact getById(Integer id);</programlisting>
+        <programlisting language="java">public Contact getById(Integer id);</programlisting>
       </para>
       <para>Quite often, only principals with permission to read the <literal>Contact</literal>
         should be allowed to obtain it. In this situation the
           <interfacename>AccessDecisionManager</interfacename> approach provided by the
           <classname>AbstractSecurityInterceptor</classname> will not suffice. This is because the
         identity of the <literal>Contact</literal> is all that is available before the secure object
         is invoked. The <classname>AclEntryAfterInvocationProvider</classname> delivers a solution,
-        and is configured as follows: <programlisting><![CDATA[
+        and is configured as follows: <programlisting language="xml"><![CDATA[
 <bean id="afterAclRead"
    class="org.springframework.security.acls.afterinvocation.AclEntryAfterInvocationProvider">
   <constructor-arg ref="aclService"/>
@@ -274,7 +274,7 @@ boolean supports(Class clazz);
           <classname>AclEntryAfterInvocationCollectionFilteringProvider</classname>. It is designed
         to remove <literal>Collection</literal> or array elements for which a principal does not
         have access. It never thrown an <classname>AccessDeniedException</classname> - simply
-        silently removes the offending elements. The provider is configured as follows: <programlisting><![CDATA[
+        silently removes the offending elements. The provider is configured as follows: <programlisting language="xml"><![CDATA[
 <bean id="afterAclCollectionRead"
   class="org.springframework.security.acls.afterinvocation.AclEntryAfterInvocationCollectionFilteringProvider">
   <constructor-arg ref="aclService"/>
@@ -311,7 +311,7 @@ boolean supports(Class clazz);
             <classname>RoleHierarchyVoter</classname>, is configured with a <interfacename>RoleHierarchy</interfacename>,
             from which it obtains all the <quote>reachable authorities</quote> which the user is assigned.
             A typical configuration might look like this:
-<programlisting><![CDATA[
+<programlisting language="xml"><![CDATA[
 <bean id="roleVoter" class="org.springframework.security.access.vote.RoleHierarchyVoter">
     <constructor-arg ref="roleHierarchy" />
 </class>

docs/manual/src/docbook/basic-and-digest-auth.xml

@@ -79,7 +79,7 @@
             a "nonce". This is a value the server generates. Spring Security's nonce adopts the
             following format:</para>
         <para>
-            <programlisting>
+            <programlisting language="txt">
   base64(expirationTime + ":" + md5Hex(expirationTime + ":" + key))
 
   expirationTime:   The date and time when the nonce expires, expressed in milliseconds
@@ -120,7 +120,7 @@
                 <literal>DigestAuthenticationFilter</literal> in the filter chain. The application
                 context will need to define the <literal>DigestAuthenticationFilter</literal> and
                 its required collaborators:</para>
-            <para> <programlisting><![CDATA[
+            <para> <programlisting language="xml"><![CDATA[
 <bean id="digestFilter" class=
     "org.springframework.security.web.authentication.www.DigestAuthenticationFilter">
   <property name="userDetailsService" ref="jdbcDaoImpl"/>

docs/manual/src/docbook/cas-auth-provider.xml

@@ -214,7 +214,7 @@
             required. </para>
         <para>You will need to add a <classname>ServiceProperties</classname> bean to your
             application context. This represents your CAS service:</para>
-        <para> <programlisting><![CDATA[
+        <para> <programlisting language="xml"><![CDATA[
   <bean id="serviceProperties"
         class="org.springframework.security.cas.ServiceProperties">
     <property name="service"
@@ -230,7 +230,7 @@
             order to gain access to the service.</para>
         <para>The following beans should be configured to commence the CAS authentication process
             (assuming you're using a namespace configuration):</para>
-        <para> <programlisting><![CDATA[
+        <para> <programlisting language="xml"><![CDATA[
 <security:http entry-point-ref="casEntryPoint">
    ...
    <custom-filter position="FORM_LOGIN_FILTER" ref="myFilter" />
@@ -262,7 +262,7 @@
             to the enterprise's CAS login server. This is where the user's browser will be
             redirected.</para>
         <para>Next you need to add a <literal>CasAuthenticationProvider</literal> and its
-            collaborators: <programlisting><![CDATA[
+            collaborators: <programlisting language="xml"><![CDATA[
   <security:authentication-manager alias="authenticationManager">
     <security:authentication-provider ref="casAuthenticationProvider" />
   </security:authentication-manager>
@@ -306,7 +306,7 @@
     <literal>ProxyTicketReceptor</literal> by adding the following to your
     web application's <literal>web.xml</literal>:</para>
 
-    <para><programlisting>
+    <para><programlisting language="xml">
 &lt;servlet&gt;
 &lt;servlet-name&gt;casproxy&lt;/servlet-name&gt;
 &lt;servlet-class&gt;edu.yale.its.tp.cas.proxy.ProxyTicketReceptor&lt;/servlet-class&gt;

docs/manual/src/docbook/channel-security.xml

@@ -37,7 +37,7 @@
             <literal>&lt;intercept-url&gt;</literal> element and this is the simplest (and
             recommended approach).</para>
         <para>To configure channel security explicitly, you would define the following the filter in
-            your application context: <programlisting><![CDATA[
+            your application context: <programlisting language="xml"><![CDATA[
 <bean id="channelProcessingFilter"
     class="org.springframework.security.web.access.channel.ChannelProcessingFilter">
   <property name="channelDecisionManager" ref="channelDecisionManager"/>

docs/manual/src/docbook/core-filters.xml

@@ -199,7 +199,7 @@
             xlink:href="#tech-intro-sec-context-persistence">Technical Overview</link> chapter so
             you might want to re-read that section at this point. Let's first take a look at how you
             would configure it for use with a <classname>FilterChainProxy</classname>. A basic
-            configuration only requires the bean itself <programlisting><![CDATA[
+            configuration only requires the bean itself <programlisting language="xml"><![CDATA[
 <bean id="securityContextPersistenceFilter"
   class="org.springframework.security.web.context.SecurityContextPersistenceFilter"/>
 ]]></programlisting> As we saw previously, this filter has two main tasks. It is responsible for
@@ -291,7 +291,7 @@ public interface SecurityContextRepository {
             </orderedlist> The login form simply contains <literal>j_username</literal> and
             <literal>j_password</literal> input fields, and posts to the URL that is monitored by
             the filter (by default this is <literal>/j_spring_security_check</literal>). The basic
-            filter configuration looks something like this: <programlisting><![CDATA[
+            filter configuration looks something like this: <programlisting language="xml"><![CDATA[
 <bean id="authenticationFilter" class=
 "org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter">
   <property name="authenticationManager" ref="authenticationManager"/>