You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ch...@apache.org on 2006/09/19 19:12:11 UTC
svn commit: r447911 -
/webservices/axis2/trunk/java/xdocs/latest/jms-transport.html
Author: chatra
Date: Tue Sep 19 10:12:11 2006
New Revision: 447911
URL: http://svn.apache.org/viewvc?view=rev&rev=447911
Log:
completed edit. Red areas need further clarifications
Modified:
webservices/axis2/trunk/java/xdocs/latest/jms-transport.html
Modified: webservices/axis2/trunk/java/xdocs/latest/jms-transport.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/latest/jms-transport.html?view=diff&rev=447911&r1=447910&r2=447911
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/jms-transport.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/jms-transport.html Tue Sep 19 10:12:11 2006
@@ -2,14 +2,14 @@
<html>
<head>
<meta http-equiv="content-type" content="">
- <title>HTTP transports</title>
+ <title>JMS Transport</title>
</head>
<body lang="en">
<h1><a name="configTransport">JMS Transport</a></h1>
-<p>This document is all about the JMS transport support in Axis2, and how it
-should be configured.</p>
+<p>This document is all about the JMS (Java Messaging Service) Transport
+support in Apache Axis2, and how it should be configured.</p>
<p><i>Send your feedback or questions to: <a
href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>. Prefix
@@ -20,24 +20,25 @@
<ul>
<li><a href="#CommonsHTTPTransportSender">Overview</a></li>
<li><a href="#timeout_config">Configuration</a></li>
+ <li><a href="#writing_services">Writing Services to Use The JMS
+ Transport</a></li>
</ul>
+<a name="CommonsHTTPTransportSender"></a>
-<h2><a name="CommonsHTTPTransportSender">Overview</a></h2>
+<h2>Overview</h2>
-<p>A new JMS transport implementation has been added to Axis2 to overcome
-some drawbacks of the previous JMS implementation. Some of the enhancements
-provided with this new implementation is the ability to assign custom JMS
-destination names or existing JMS destinations to Axis2 services being
-deployed. </p>
-
-<p></p>
+<p>A new JMS or Java Messaging Service transport implementation has been
+added to Axis2 to overcome some drawbacks of the previous JMS implementation.
+Some of the enhancements provided with this new implementation is the ability
+to <strong>assign custom JMS destination names or existing JMS destinations
+to Axis2 services being deployed</strong>.</p>
+<a name="timeout_config"></a>
<h2>Configuration</h2>
<p>To use the JMS transport, the axis2.xml configuration must be setup as
-follows, to configure the JMSListener and the JMS Sender</p>
-<pre>
-axis2.xml
+follows in order to configure the JMSListener and the JMS Sender</p>
+<pre><strong>axis2.xml</strong>
<transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
<parameter name="default" locked="false">
<parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
@@ -46,22 +47,21 @@
</parameter>
</transportReceiver>
- <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender"/>
-</pre>
+ <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender"/></pre>
<p>The JMS transport receiver configuration allows you to define the default
connection factory (named as "default" ~ JMSConstants.DEFAULT_CONFAC_NAME)
for use by Axis2 services using the JMS transport. This connection factory
would be used by any service which does not explicitly specify a connection
-factory name in its services.xml. The configuration required to associate a
-(local) Axis2 connection factory to an actual implementation must be provided
-as shown above, to specify the JNDI URL, initial context factory class and
-the JNDI name of the actual JMS connection factory to be used. You may also
-specify the parameters "java.naming.security.principal" and
-"java.naming.security.credentials" if required, to access the actual
-connection factory. The example shown above uses an ActiveMQ JMS
-implementation.</p>
-<pre>axis2.xml
+factory name in its services.xml. <span style="color: #FF0000">The
+configuration required to associate a (local) Axis2 connection factory to an
+actual implementation must be provided as shown above, to specify the JNDI
+URL, initial context factory class and the JNDI name of the actual JMS
+connection factory to be used.</span> You may also specify the parameters
+"java.naming.security.principal" and "java.naming.security.credentials" if
+required, to access the actual connection factory. The example shown above
+uses an ActiveMQ JMS implementation.</p>
+<pre><strong>axis2.xml</strong>
<parameter name="myTopicConnectionFactory" locked="false"></pre>
<pre> <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter></pre>
<pre> <parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter></pre>
@@ -71,14 +71,14 @@
<p>If it is required or applicable, you are free to define additional (local)
connection factories to Axis2 as shown above, which your services may use.
For a service to specify that such a connection factory should be used, its
-services.xml may specify the following configuration parameter.</p>
+services.xml may specify the following configuration parameter:</p>
<pre>services.xml
<parameter name="transport.jms.ConnectionFactory" locked="true">myTopicConnectionFactory</parameter></pre>
-<p>Note: Depending on your JMS implementation, you will need to make
-available all required libraries to your Axis2 instance. This example assumes
-you are using an ActiveMQ instance. To run the given code samples, it
-required me to make available the following JAR files:
+<p><strong>Note:</strong> Depending on your JMS implementation, you will need
+to make available all required libraries to your Axis2 instance. This example
+assumes you are using an ActiveMQ instance. To run the given code samples, it
+was required to make available the following JAR files:
activeio-core-3.0-beta1.jar, activemq-core-4.0-RC2.jar,
geronimo-j2ee-management_1.0_spec-1.0.jar at a minimum. It also requires you
to start ActiveMQ separately from Axis2, and then provide the appropriate
@@ -89,9 +89,9 @@
pool to process received messages.</p>
<p>A service on an Axis2 instance is deployed on all started transports by
-default, unless a list of transports are specified in its services.xml. Hence
-if a service must only be deployed on JMS, you should specify it on the
-services.xml as follows:</p>
+default, unless a list of transports are specified in its services.xml.
+Hence, if a service must only be deployed on JMS, you should specify it on
+the services.xml as follows:</p>
<pre> <transports>
<transport>jms</transport>
</transports></pre>
@@ -101,21 +101,21 @@
<strong>Queue</strong> by the same name as the <strong>name of the
service</strong>. If an explicit connection factory definition name has not
been specified, it is assumed that the "default" connection factory
-definition configured within the transport receiver should be used. To
-provide a custom JMS destination name and connection factory, the
-services.xml could provide the following optional parameters.</p>
+definition configured within the transport receiver be used. To provide a
+custom JMS destination name and connection factory, the services.xml could
+provide the following optional parameters.</p>
<pre> <parameter name="transport.jms.ConnectionFactory" locked="true">myTopicConnectionFactory</parameter>
<parameter name="transport.jms.Destination" locked="true">dynamicTopics/something.TestTopic</parameter></pre>
+<a name="writing_services"></a>
-<h2>Writing services to use the JMS transport</h2>
+<h2>Writing Services to Use The JMS Transport</h2>
-<p>This section assumes that you are already familiar with writing service
-implementations for Axis2, and provides information to enable you to write
-your own service implementations which are exposed over JMS.</p>
-
-<p></p>
+<p>This section assumes that you are already familiar with <a href=""><span
+style="color: #FF0000">writing service implementations</span></a> for Axis2,
+and provides information to enable you to write your own service
+implementations which are exposed over JMS.</p>
-<p>Echo - Service implementation and services.xml</p>
+<p><strong>Echo - Service implementation and services.xml</strong></p>
<p>This sample demonstrates a very simple service which is to be exposed over
JMS. It does not specify a custom connection factory name and hence uses the
@@ -123,10 +123,10 @@
does not specify a custom destination name, and hence would listen to
messages over a JMS Queue named "Echo" (which is the name of the service).
This service will be exposed over all defined Axis2 transports, and the
-resulting URL for the service over JMS would be</p>
+resulting URL for the service over JMS would be:</p>
<p></p>
-<pre>Echo.java</pre>
+<pre><strong>Echo.java</strong></pre>
<pre> public class Echo {</pre>
<pre> public String echoString(String in) {</pre>
<pre> return in;</pre>
@@ -139,7 +139,7 @@
<pre> }</pre>
<pre> }</pre>
<pre></pre>
-<pre>services.xml</pre>
+<pre><strong>services.xml</strong></pre>
<pre> <service name="echo"></pre>
<pre> <description>Echo Service</description></pre>
<pre> <messageReceivers></pre>
@@ -153,21 +153,21 @@
<p></p>
-<p>Echo2 - Service implementation and services.xml</p>
+<p><strong>Echo2 - Service implementation and services.xml</strong></p>
<p>This example shows a simple service which specifies that it should only be
exposed over the JMS transport, and that the custom connection factory named
-"myTopcConnectionFactory" should be used to listen for requests, at the JMS
+"myTopcConnectionFactory" should be used to listen for requests at the JMS
destination named "dynamicTopics/something.TestTopic". The JMS URL to access
-this service is</p>
-<pre>Echo2.java</pre>
+this service is:</p>
+<pre><strong>Echo2.java</strong></pre>
<pre> public class Echo2 {</pre>
<pre> public String echoString(String in) {</pre>
<pre> return in;</pre>
<pre> }</pre>
<pre> }</pre>
<pre></pre>
-<pre>services.xml</pre>
+<pre><strong>services.xml</strong></pre>
<pre> <service name="echo"></pre>
<pre> <transports></pre>
<pre> <transport>jms</transport></pre>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org