Use Spring JMS to simplify Asynchronous Message Processing

Http://www.onjava.com/lpt/a/6490

This article describes how Spring simplifies asynchronous message calls. It uses a loan example to explain how Spring reduces

The amount in development.

The following is the amount of code required by traditional development.

public void sendMessage() {    queueName = "queue/CreditRequestSendQueue";    System.out.println("Queue name is " + queueName);    /*     * Create JNDI Initial Context     */    try {        Hashtable env = new Hashtable();        env.put("java.naming.factory.initial",            "org.jnp.interfaces.NamingContextFactory");        env.put("java.naming.provider.url","localhost");        env.put("java.naming.factory.url.pkgs",            "org.jnp.interfaces:org.jboss.naming");        jndiContext = new InitialContext(env);    } catch (NamingException e) {        System.out.println("Could not create JNDI API " +            "context: " + e.toString());    }    /*     * Get queue connection factory and queue objects from JNDI context.     */    try {        queueConnectionFactory = (QueueConnectionFactory)        jndiContext.lookup("UIL2ConnectionFactory");        queue = (Queue) jndiContext.lookup(queueName);    } catch (NamingException e) {        System.out.println("JNDI API lookup failed: " +            e.toString());    }    /*     * Create connection, session, sender objects.     * Send the message.     * Cleanup JMS connection.     */    try {        queueConnection =            queueConnectionFactory.createQueueConnection();        queueSession = queueConnection.createQueueSession(false,                Session.AUTO_ACKNOWLEDGE);        queueSender = queueSession.createSender(queue);        message = queueSession.createTextMessage();        message.setText("This is a sample JMS message.");        System.out.println("Sending message: " + message.getText());        queueSender.send(message);    } catch (JMSException e) {        System.out.println("Exception occurred: " + e.toString());    } finally {        if (queueConnection != null) {            try {                queueConnection.close();            } catch (JMSException e) {}        }    }}

Then the Spring code

public void send() {    try {        ClassPathXmlApplicationContext appContext = new 

ClassPathXmlApplicationContext(new String[] {                "spring-jms.xml"});        System.out.println("Classpath loaded");        JMSSender jmsSender = (JMSSender)appContext.getBean("jmsSender");        jmsSender.sendMesage();        System.out.println("Message sent using Spring JMS.");    } catch(Exception e) {        e.printStackTrace();    }}

On the surface, Spring wins, and the code is much less, but let's take a look at the XML configuration of Spring.

  
   
    
     
                      org.jnp.interfaces.NamingContextFactory            
     
     
                      localhost            
     
     
                      org.jnp.interfaces:org.jboss.naming            
     
    
   
  
  
   
    
   
   
    
     UIL2ConnectionFactory
    
   
  
   
    
     
    
    
     
      queue/CreditRequestSendQueue
     
    
   
   
    
     
    
    
     
      queue/CreditReqeustReceiveQueue
     
    
   
   
    
     
    
    
     
    
    
     
      30000
     
    
   
   
    
     
    
   
   
    
     
    
   
 
We began to recognize the true face of Spring. The configuration with no headers is a nightmare of XML. From chaos to chaos.
 
 
Trackback: http://tb.blog.csdn.net/TrackBack.aspx? PostId = 607922