아름다운프로'의 JTOP.org 백업사이트

소스는 ActiveMQ의 소스와 같으며, 해당 xml은 아래와 같다.

sonicmq_receive.xml

<?xml version="1.0" encoding="euc-kr"?>

<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">



<beans>	

	

	<bean id="start" class="java.lang.String"/>

	

	<bean id="connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">

		<property name="jndiTemplate">

      		<ref bean="jndiTemplate"/>

   		</property>

   		<property name="jndiName">

      		<value>OUTTER_CB_URL</value>

   		</property>

	</bean>

	

	<bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">

		<property name="environment">

			<props>

				<prop key="java.naming.factory.initial">

					com.sonicsw.jndi.mfcontext.MFContextFactory

				</prop>

				<prop key="java.naming.provider.url">

					tcp://222.112.180.61:2506

				</prop>

				<prop key="com.sonicsw.jndi.mfcontext.domain">

					Domain1

				</prop>

				<prop key="java.naming.security.principal">

					Administrator

				</prop>

				<prop key="java.naming.security.credentials">

					Administrator

				</prop>

			</props>

		</property>

	</bean>



	<bean id="destination" class="org.springframework.jndi.JndiObjectFactoryBean">

		<property name="jndiTemplate">

			<ref bean="jndiTemplate" />

		</property>

		<property name="jndiName">

			<value>T1</value>

		</property>

	</bean>

		

	<bean id="messageListener" class="org.jtop.spirng.sample.sonicmq.receive.Receiver" />

		

	<bean id="listenerContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer">

		<property name="connectionFactory" ref="connectionFactory" />

		<property name="destination" ref="destination" />

		<property name="messageListener" ref="messageListener" />

	</bean>

</beans>

<?xml version="1.0" encoding="euc-kr"?>

<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">



<beans>	

	

	<bean id="connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">

		<property name="jndiTemplate">

      		<ref bean="jndiTemplate"/>

   		</property>

   		<property name="jndiName">

      		<value>OUTTER_CB_URL</value>

   		</property>

	</bean>

		

	<bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">

		<property name="environment">

			<props>

				<prop key="java.naming.factory.initial">

					com.sonicsw.jndi.mfcontext.MFContextFactory

				</prop>

				<prop key="java.naming.provider.url">

					tcp://222.112.180.61:2506

				</prop>

				<prop key="com.sonicsw.jndi.mfcontext.domain">

					Domain1

				</prop>

				<prop key="java.naming.security.principal">

					Administrator

				</prop>

				<prop key="java.naming.security.credentials">

					Administrator

				</prop>

			</props>

		</property>

	</bean>

	

	<bean id="destination" class="org.springframework.jndi.JndiObjectFactoryBean">

		<property name="jndiTemplate">

			<ref bean="jndiTemplate" />

		</property>

		<property name="jndiName">

			<value>T1</value>

		</property>

	</bean>

	

	<bean id="rankSender" class="org.jtop.spirng.sample.sonicmq.send.Sender">

		<property name="connectionFactory" ref="connectionFactory" />

		<property name="destination" ref="destination" />

	</bean>

</beans>

메시지 받기 (onMessage)



package org.jtop.spirng.sample.activemq.receive;



import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.MessageListener;

import javax.jms.TextMessage;



import org.apache.commons.logging.Log;

import org.apache.commons.logging.LogFactory;



/**

 * 

 * @author lee

 */

public class Receiver implements MessageListener {

	

	Log log = LogFactory.getLog(this.getClass());

	

	public void onMessage(Message message) {

		try {

			TextMessage tm = (TextMessage)message;

			log.debug("Property : " + tm.getStringProperty("Property"));

			log.debug("Text : " + tm.getText());

		} catch (JMSException e) {

			log.error("onMessage Exception : ", e);

		}

	}

}





실행하는 클래스



package org.jtop.spirng.sample.activemq.receive;



import org.apache.commons.logging.Log;

import org.apache.commons.logging.LogFactory;

import org.springframework.context.ApplicationContext;

import org.springframework.context.support.FileSystemXmlApplicationContext;



public class Runner{

	

	Log log = LogFactory.getLog(this.getClass());

	

	private void run() {

		ApplicationContext ctx = new FileSystemXmlApplicationContext("conf/activemq/activemq_receive.xml");

		ctx.getBean("start");

		log.info("============= onMeesage() ==============");

	}



	public static void main(String[] args) {

		Runner job = new Runner();

		job.run();

	}

}







activemq_receive.xml 내용



<?xml version="1.0" encoding="euc-kr"?>

<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">



<beans>	

	

	<!-- === XML이 로딩되면서 자동으로 messageListener 동작(start는 단순 로딩용) === -->

	<bean id="start" class="java.lang.String"/>

	

	<bean id="r_connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">

		<property name="jndiTemplate">

      		<ref bean="r_jndiTemplate"/>

   		</property>

   		<property name="jndiName">

      		<value>ConnectionFactory</value>

   		</property>

	</bean>

	

	<bean id="r_jndiTemplate" class="org.springframework.jndi.JndiTemplate">

		<property name="environment">

			<props>

				<prop key="java.naming.factory.initial">

					org.apache.activemq.jndi.ActiveMQInitialContextFactory

				</prop>

				<prop key="java.naming.provider.url">

					tcp://localhost:61616

				</prop>				

			</props>

		</property>

	</bean>

	

	<bean id="r_destination" class="org.apache.activemq.command.ActiveMQTopic" autowire="constructor">

		<constructor-arg value="FOO.BAR" />

	</bean>

	

	<bean id="messageListener" class="org.jtop.spirng.sample.activemq.receive.Receiver" />

	

	<bean id="listenerContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer">

		<property name="connectionFactory" ref="r_connectionFactory" />

		<property name="destination" ref="r_destination" />

		<property name="messageListener" ref="messageListener" />

	</bean>

		

</beans>

두 MQ모두 Sample(or Example)에 보면 Connection 생성에서부터 각자의 Connection 클래스로 생성하게

되어 있어, 한쪽에서 개발을 한 다음에는 다른 MQ로의 사용이 어렵게 되어 있다.

이에 Spring의 JmsTemplate을 사용하여, 좀 더 쉬운 방법으로의 통합된 형태의 간단한 예제를 작성해본다.

(단, JmsTemplate Gotchas 을 읽어보고, JmsTemplate을 적용에 주의를 요한다.)



메시지 Send 



package org.jtop.spirng.sample.activemq.send;



import javax.jms.ConnectionFactory;

import javax.jms.Destination;

import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.Session;



import org.apache.commons.logging.Log;

import org.apache.commons.logging.LogFactory;

import org.springframework.jms.core.JmsTemplate;

import org.springframework.jms.core.MessageCreator;



public class Sender {

	

	Log log = LogFactory.getLog(this.getClass());

	

	private JmsTemplate jmsTemplate;

	private Destination destination;

	

	public void setConnectionFactory(ConnectionFactory cf){

		jmsTemplate = new JmsTemplate(cf);

	}

	

	public void setDestination(Destination des){

		this.destination = des;

	}

	

	public void send(){

		this.jmsTemplate.send(this.destination, new MessageCreator(){

			public Message createMessage(Session session) throws JMSException {

				Message ms = session.createTextMessage("Example Message");

				ms.setStringProperty("Property", "Example");

				return ms;

			}

		});

	}

}



실행하는 클래스



package org.jtop.spirng.sample.activemq.send;



import org.apache.commons.logging.Log;

import org.apache.commons.logging.LogFactory;

import org.springframework.context.ApplicationContext;

import org.springframework.context.support.FileSystemXmlApplicationContext;



public class Runner{

	

	Log log = LogFactory.getLog(this.getClass());

	

	private void run() {

		ApplicationContext ctx = new FileSystemXmlApplicationContext("conf/activemq/activemq_send.xml");

		Sender sender = (Sender)ctx.getBean("sender");

		sender.send();

		log.info("============= Send ==============");

	}



	public static void main(String[] args) {

		Runner job = new Runner();

		job.run();

	}

}



activemq_send.xml 내용



<?xml version="1.0" encoding="euc-kr"?>

<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">



<beans>	

	<!-- ======================== Sender =========================== -->

	<bean id="s_connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">

		<property name="jndiTemplate">

      		<ref bean="s_jndiTemplate"/>

   		</property>

   		<property name="jndiName">

      		<value>ConnectionFactory</value>

   		</property>

	</bean>

	

	<bean id="s_jndiTemplate" class="org.springframework.jndi.JndiTemplate">

		<property name="environment">

			<props>

				<prop key="java.naming.factory.initial">

					org.apache.activemq.jndi.ActiveMQInitialContextFactory

				</prop>

				<prop key="java.naming.provider.url">

					tcp://localhost:61616

				</prop>				

			</props>

		</property>

	</bean>

	

	<bean id="s_destination" class="org.apache.activemq.command.ActiveMQTopic" autowire="constructor">

		<constructor-arg value="FOO.BAR" />

	</bean>

	

	<bean id="sender" class="org.jtop.spirng.sample.activemq.send.Sender">

		<property name="connectionFactory" ref="s_connectionFactory" />

		<property name="destination" ref="s_destination" />		

	</bean>	

</beans>

Description

Maintenance
version of the Java^TM Message Service specification, version 1.1.

Specification Lead

Kate Stout,
Sun Microsystems, Inc.

Feedback

This maintenance
release addresses the unification of the programming interfaces for the Point-to-Point
and Pub/Sub messaging domains in the Java Message Service (JMS) API. In the
existing version of the specification, the client programming model make
a strong distinction between these two domains. One consequence of domain 
separation is that actions from the Point-to-Point domain and the Pub/Sub
domain in can not be used in the same transaction.

In this proposed
domain unification of the interfaces, methods have been added to support
the ability to include PTP and Pub/Sub messaging in the same transaction.
In addition, the domain unification proposed simplifies the client programming
model, so that the client programmer can use a simplified set of APIs to create
an application.

This proposal
is

Fully backwards compatible;
existing implementations will work as is.









Semantically compatible;
semantic differences between the two messaging domains are retained

Domain unification

ConnectionConsumer
createConnectionConsumer(Destination destination, String messageSelector,
ServerSessionPool sessionPool, int maxMessages) throws JMSException;

ConnectionConsumer createDurableConnectionConsumer(Topic topic,String
subscriptionName, String messageSelector, ServerSessionPool sessionPool,
int maxMessages) throws JMSException;

Session createSession(boolean transacted, int acknowledgeMode) throws
JMSException;

Connection createConnection() throws JMSException;

Connection createConnection(String userName, String password) throws
JMSException;

Destination getDestination() throws JMSException;

void send(Message message) throws JMSException;

void send(Message message, int deliveryMode, int priority, long timeToLive)
throws JMSException;

void send(Destination destination, Message message) throws JMSException;

void send(Destination destination, Message message, int deliveryMode,
int priority, long timeToLive) throws JMSException;

MessageProducer createProducer(Destination destination) throws JMSException;

MessageConsumer createConsumer(Destination destination) throws JMSException;

MessageConsumer createConsumer(Destination destination, java.lang.String
messageSelector) throws JMSException;

MessageConsumer createConsumer(Destination destination, java.lang.String
messageSelector, boolean NoLocal) throws JMSException;

TopicSubscriber createDurableSubscriber(Topic topic, java.lang.String
name) throws JMSException;

TopicSubscriber createDurableSubscriber(Topic topic, java.lang.String
name, java.lang.String messageSelector, boolean noLocal) throws JMSException;

QueueBrowser createBrowser(Queue queue) throws JMSException;

QueueBrowser createBrowser(Queue queue, String messageSelector) throws
JMSException;

Queue createQueue(String name) throws JMSException;

Topic createTopic(String name) throws JMSException;

TemporaryTopic createTemporaryTopic() throws JMSException;

TemporaryQueue createTemporaryQueue() throws JMSException;

void unsubscribe(String string name)

XASession createXASession() throws JMSException;

XAConnection createXAConnection() throws JMSException;

XAConnection createXAConnection(String userName, String password)
throws JMSException;

int getBodyLength() throws JMSException

int getAcknowledgeMode() throws JMSException

Example 1: Setting up a connection and session



JMS 1.0.2b



JMS 1.1


 

Example
2: Creating a Message Producer to a topic



JMS 1.0.2b



JMS 1.1


 

Example
3 - Adding a Message Producer to a queue



JMS 1.0.2b



JMS 1.1

// Look up connection factory and topic.

topicConnectionFactory = (TopicConnectionFactory)

topicConnection = topicConnectionFactory.createConnection();

JMS 1.1

Use ConnectionFactory, Connection and Session to setup.

Context jndiContext = null;

// Look up connection factory and topic.

Example
2: Creating a message producer (to a topic)

Set a message producer that can send messages

JMS 1.0.2.b

Sets up a TopicPublisher and sends messages on a TopicSession


 

// Create a TopicPublisher and send a message

TopicPublisher topicPublisher = null;

// Create a Message Producer and send a message

MessageProducer messageProducer = null;

Example
3: Adding a Message Producer to a queue

The client programming simplification can be seen if we now try to add a
Message producer that will send messages to a Queue.

 

JMS 1.0.2b

To do this, the application must:

Lookup QueueConnectionFactory




Lookup Queue




Create QueueConnection




Create QueueSession




Create QueueSender




Create Message




send message using QueueSender.send();

JMS 1.1

By contrast, the unified model can re-use the Connection and Session that
has already been established. The additional steps are:

Lookup Queue




Create MessageProducer




Create Message




Send message using MessageProducer.send()

MessageProducer workFlowProducer = null;