Fix source code language

Author: eric-schneider

modules/ROOT/pages/pulsar-jms-faq.adoc

@@ -29,14 +29,14 @@ In the tck-executor module you'll find:
 
 To build the package, run unit tests, and run the TCK:
 
-[source,language-bash]
+[source,bash]
 ----
 mvn clean install -Prun-tck
 ----
 
 To run only the TCK:
 
-[source,language-bash]
+[source,bash]
 ----
 mvn clean install -Prun-tck -am -DskipTests -pl tck-executor
 ----
@@ -57,14 +57,14 @@ If you'd like to fork or contribute to Starlight for JMS:
 
 . Clone the git repo:
 +
-[source,language-bash]
+[source,bash]
 ----
 git clone [email protected]:datastax/pulsar-jms.git
 ----
 
 . Build using Maven:
 +
-[source,language-bash]
+[source,bash]
 ----
 mvn clean install
 ----

modules/examples/pages/pulsar-jms-implementation.adoc

@@ -35,7 +35,7 @@ When you set a `clientId`, the actual subscription name in Pulsar is constructed
 One solution for this situation is the *dead letter topic* policy. The *dead-letter topic* policy routes the unsuccessful messages to the *dead-letter topic* for storage, so consumers can keep consuming while the unsuccessful messages are stored in the dead-letter topic for processing or evaluation.
 
 Starlight for JMS allows further configuration of `deadLetterPolicy`. For more on `deadLetterTopic` configuration properties, see xref:reference:pulsar-jms-reference.adoc[].
-[source,language-java]
+[source,java]
 ----
 Map<String, Object> deadLetterPolicy = new HashMap<>();
     consumerConfig.put("deadLetterPolicy", deadLetterPolicy);

modules/jms-migration/pages/pulsar-jms-install.adoc

@@ -14,7 +14,7 @@ To avoid issues, DataStax recommends using: +
 
 Install Starlight for JMS by adding the following dependency to your Java Maven project `pom.xml`. Remember to choose the most recent version.
 
-[source,language-xml]
+[source,xml]
 ----
 <dependency>
    <artifactId>pulsar-jms</artifactId>
@@ -27,7 +27,7 @@ That file contains only Starlight for JMS code and transitively imports the Apac
 
 You can also use a "fat" JAR that includes all dependencies:
 
-[source,language-xml]
+[source,xml]
 ----
 <dependency>
    <artifactId>pulsar-jms-all</artifactId>

modules/jms-migration/pages/pulsar-jms-quickstart-sa.adoc

@@ -22,14 +22,14 @@ To install a Docker Pulsar instance:
 . Make sure you have https://docs.docker.com/get-docker/[Docker] installed on your platform.
 . Open a terminal and create a Pulsar Docker instance:
 +
-[source,language-bash]
+[source,bash]
 ----
 docker run --name pulsar-jms-runner -p 8080:8080 -p 6650:6650 apachepulsar/pulsar:latest /pulsar/bin/pulsar standalone
 ----
 +
 *Results*:
 +
-[source,language-bash]
+[source,bash]
 ----
 Many status messages...
 
@@ -51,7 +51,7 @@ We'll use Apache Maven to handle dependency management so you don't have to manu
 . Create a project directory in a convenient location.
 . Save the following file as `pom.xml` in your project directory.
 +
-[source,language-xml]
+[source,xml]
 ----
 <?xml version="1.0" encoding="UTF-8"?>
 <project>
@@ -127,15 +127,15 @@ To create the standalone example app:
 
 . In the project directory you created above, create the following directory hierarchy, `<project-directory>/src/main/java/example`:
 +
-[source,language-bash]
+[source,bash]
 ----
 cd <project-directory>
 mkdir -p /src/main/java/example
 ----
 +
 . Copy the following code into a file named `StandaloneTest.java` and save the file:
 +
-[source,language-java]
+[source,java]
 ----
 package example;
 
@@ -201,14 +201,14 @@ To compile the sample application:
 . Change to the `<product_directory`.
 . Run the maven command:
 +
-[source,language-bash]
+[source,bash]
 ----
 mvn clean install
 ----
 +
 *Results*:
 +
-[source,language-bash]
+[source,bash]
 ----
 Many status messages...
 
@@ -229,14 +229,14 @@ TIP: The first time you compile the JAR file, Maven downloads all required depen
 
 To run the sample app, from the `<product_directory`:
 
-[source,language-bash]
+[source,bash]
 ----
 java -jar target/pulsar-fast-jms-example-1.0-jar-with-dependencies.jar
 ----
 
 *Results*:
 
-[source,language-bash]
+[source,bash]
 ----
 Sending: Hello world! 0
 
@@ -277,14 +277,14 @@ To delete the Pulsar Docker container:
 
 . Get a list of all Docker containers and note the container ID (`5116f0d16eb3` in the example):
 +
-[source,language-bash]
+[source,bash]
 ----
 docker ps --all
 ----
 +
 *Results*:
 +
-[source,language-bash]
+[source,bash]
 ----
 CONTAINER ID   IMAGE                        COMMAND                  CREATED       STATUS                       PORTS                  NAMES
 5116f0d16eb3   apachepulsar/pulsar:latest   "/pulsar/bin/pulsar …"   2 hours ago   Exited (130) 2 minutes ago                          pulsar-jms-runner
@@ -293,14 +293,14 @@ CONTAINER ID   IMAGE                        COMMAND                  CREATED
 +
 . Delete the container using the container ID:
 +
-[source,language-bash]
+[source,bash]
 ----
 docker rm 5116f0d16eb3
 ----
 +
 *Results*:
 +
-[source,language-bash]
+[source,bash]
 ----
 5116f0d16eb3
 ----

modules/reference/pages/pulsar-jms-mappings.adoc

@@ -77,7 +77,7 @@ NOTE: In certain cases, the `peekMessages` API can return the last consumed mess
 By default, the subscription created by a JMS queue is named `jms-queue`, which can be overriden with `jms.queueSubscriptionName` in the `PulsarConnectionFactory` constructor.
 
 You can instead set the subscription name at queue creation:
-[source,language-java]
+[source,java]
 ----
 try (PulsarConnectionFactory factory = new PulsarConnectionFactory(properties); ){
     Queue queue = session.createQueue("pulsarQueue:subscriptionName");
@@ -87,7 +87,7 @@ try (PulsarConnectionFactory factory = new PulsarConnectionFactory(properties);
 In the above example, the subscription will be `subscriptionName`, and the queue will be backed by the `public/default/pulsarQueue` Pulsar topic. +
 
 You can override the default `public/default` namespace with `jms.systemNamespace` in the `PulsarConnectionFactory` constructor:
-[source,language-java]
+[source,java]
 ----
 Map<String, Object> configuration = new HashMap<>();
 configuration.put("jms.systemNamespace", "<my-tenant>/<my-namespace>");
@@ -97,7 +97,7 @@ factory.close();
 ----
 
 A fully-qualified namespace works similarly, but the topic destination points to a persistent topic URL:
-[source,language-java]
+[source,java]
 ----
 Queue queue = session.createQueue("persistent://tenant/namespace/pulsarQueue:subscriptionName")
 ----
@@ -109,14 +109,14 @@ In the above example, the subscription will be `subscriptionName`, and the queue
 By default, the `jms.precreateQueueSubscription` configuration flag is set to `true`, and the JMS client will pre-create the `jms-queue` subscription (see xref:pulsar-jms-mappings.adoc#jms-queue[Overriding jms-queue] above). +
 
 To disable automatic subscription creation in the JMS client, set the `jms.precreateQueueSubscription` parameter to `false`, as below:
-[source,language-java]
+[source,java]
 ----
 Map<String, Object> properties = new HashMap<>();
     properties.put("jms.precreateQueueSubscription", "false");
 ----
 
 To disable automatic subscription creation on the Pulsar broker, set the `allowAutoSubscriptionCreation` parameter to `false`, as below:
-[source,language-java]
+[source,java]
 ----
 public static void before() throws Exception {
     cluster =

modules/reference/pages/pulsar-jms-reference.adoc

@@ -5,7 +5,7 @@ A complete configuration reference for Starlight for JMS.
 
 Configuration information is passed to the `PulsarConnectionFactory` constructor:
 
-[source,language-java]
+[source,java]
 ----
 Map<String, Object> configuration = new HashMap<>();
 configuration.put("...","...");
@@ -16,7 +16,7 @@ factory.close();
 
 Configuration information can also be passed as a JSON encoded string:
 
-[source,language-java]
+[source,java]
 ----
 String configuration = "{.....}";
 ConnectionFactory factory = new PulsarConnectionFactory();
@@ -29,7 +29,7 @@ Configuration information can be passed when a `JMSContext` or `Session` is crea
 
 Create a `PulsarConnectionFactory` with `initialContext` for configuration.
 
-[source,language-java]
+[source,java]
 ----
 Map<String, Object> configuration = new HashMap<>();
 Map<String, Object> consumerConfig = new HashMap<>();
@@ -40,7 +40,7 @@ PulsarJMSContext initialContext = (PulsarJMSContext) factory.createContext();
 
 The initial configuration in `initialContext` will be overridden by the subsequent `JMSContext` configuration `withCustomConfiguration`.
 
-[source,language-java]
+[source,java]
 ----
 Map<String, Object> perContextConfiguration new HashMap<>();
 Map<String, Object> perContextConsumerConfig = new HashMap<>();
@@ -50,7 +50,7 @@ JMSContext withCustomConfiguration = initialContext.createContext(mode, perConte
 
 Or override the initial configuration in `initialContext` with the `JMSContext` configuration `withCustomConfiguration` in a Session object.
 
-[source,language-java]
+[source,java]
 ----
 Session.createSession(int mode, Map<String, Object> withCustomConfiguration)
 ----