activemq-artemis/examples/javaee/mdb-cmt-tx-not-supported/readme.html

116 lines
4.6 KiB
HTML

<html>
<head>
<title>HornetQ Java EE MDB Container Managed Transaction with NOT_SUPPORTED transaction Example</title>
<link rel="stylesheet" type="text/css" href="../../common/common.css" />
<link rel="stylesheet" type="text/css" href="../../common/prettify.css" />
<script type="text/javascript" src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
<h1>Java EE MDB Container Managed Transaction with NOT_SUPPORTED transaction Example</h1>
<p>This example shows you how to send a message to an MDB</p>
<p>The example will deploy a simple MDB and send a message. The MDB consuming it will not use a transaction.</p>
<p>The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.</p>
<h2>Example step-by-step</h2>
<p><i>download WildFly 8.0.0.Final from <a href="http://wildfly.org/downloads/">here</a> and install.</i></p>
<p><i>set the JBOSS_HOME property to point to the WildFly install directory</i></p>
<p><i>type <code>mvn verify</code> from the example directory to run</i></p>
<ol>
<li>First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the <code>jndi.properties</code> file in the directory <code>config</code></li>
<pre class="prettyprint">
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080");
initialContext = new InitialContext(env);
</pre>
<li>We look up the JMS queue object from JNDI</li>
<pre class="prettyprint">
Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
</pre>
<li>We look up the JMS connection factory object from JNDI</li>
<pre class="prettyprint">
ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
</pre>
<li>We create a JMS connection</li>
<pre class="prettyprint">
connection = cf.createConnection("guest", "password");
</pre>
<li>We create a JMS session. The session is created as non transacted and will auto acknowledge messages.</li>
<pre class="prettyprint">
<code>Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);</code>
</pre>
<li>We create a JMS message producer on the session. This will be used to send the messages.</li>
<pre class="prettyprint">
<code>MessageProducer messageProducer = session.createProducer(queue);</code>
</pre>
<li>We create a JMS text messages that we are going to send.</li>
<pre class="prettyprint">
<code> TextMessage message = session.createTextMessage("This is a text message");</code>
</pre>
<li>We send messages to the queue</li>
<pre class="prettyprint">
<code>messageProducer.send(message);</code>
</pre>
<li>The MDB receives the message<br />
We know the message is a TextMessage so we cast to it.
</li>
<pre class="prettyprint">
<code>TextMessage tm = (TextMessage)message;</code>
</pre>
<li>The MDB gets the text and prints it
</li>
<pre class="prettyprint">
<code>String text = tm.getText();
System.out.println("message " + text + " received");
</code>
</pre>
<li>We look at the transaction to make sure there isn't one
</li>
<pre class="prettyprint">
<code>Transaction tx = tm.getTransaction();
if(tx == null)
{
System.out.println("tx is null, just as expected");
}
</code>
</pre>
<li>And finally, <b>always</b> remember to close your JMS connections and resources after use, in a <code>finally</code> block. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects</li>
<pre class="prettyprint">
<code>finally
{
if (initialContext != null)
{
initialContext.close();
}
if (connection != null)
{
connection.close();
}
}</code>
</pre>
</ol>
</body>
</html>