svn commit: r763440 - /webservices/commons/trunk/modules/transport/src/site/apt/jms.apt

[ve...@apache.org]

Author: veithen
Date: Wed Apr  8 22:45:31 2009
New Revision: 763440

URL: http://svn.apache.org/viewvc?rev=763440&view=rev
Log:
Added some documentation about topics recently discussed on the Synapse mailing list.

Modified:
    webservices/commons/trunk/modules/transport/src/site/apt/jms.apt

Modified: webservices/commons/trunk/modules/transport/src/site/apt/jms.apt
URL: http://svn.apache.org/viewvc/webservices/commons/trunk/modules/transport/src/site/apt/jms.apt?rev=763440&r1=763439&r2=763440&view=diff
==============================================================================
--- webservices/commons/trunk/modules/transport/src/site/apt/jms.apt (original)
+++ webservices/commons/trunk/modules/transport/src/site/apt/jms.apt Wed Apr  8 22:45:31 2009
@@ -63,6 +63,23 @@
 
     As explained below, for the JMS sender configuration it is not mandatory (but recommended) to specify
     connection factories.
+    
+    The parameters that may appear in a connection factory configuration are defined as follows:
+    
+      [java.naming.factory.initial]
+      TODO
+      
+      [java.naming.provider.url]
+      TODO
+      
+      [transport.jms.ConnectionFactoryJNDIName]
+      TODO
+      
+      [transport.jms.JMSSpecVersion]
+      TODO
+      
+      [transport.jms.CacheLevel]
+      TODO
 
 * {JMS connections and message dispatching}
 
@@ -180,11 +197,16 @@
 
 * {Endpoint references}
 
+  Endpoint references for the JMS transport must have the following form:
+  
 +--------------------------------------------+
-jms-epr = "jms:/" jms-dest [ "?" param  *( [ "&" param ] ) ]
+jms-epr = "jms:/" jms-dest [ "?" param  *( [ "&" param ] ) ]
 param = param-name "=" param-value
 +--------------------------------------------+
 
+  <<<jms-dest>>> is the JNDI name of the destination to send the message to. The parameters are
+  defined as follows:
+
   [transport.jms.ConnectionFactoryJNDIName]
   TODO
   
@@ -212,6 +234,14 @@
   [java.naming.security.credentials]
   TODO
 
+  []
+  
+  The JMS sender will check if the transport configuration contains a connection factory compatible
+  with the settings specified in the endpoint URL. If a matching configuration is found, the
+  sender will reuse the cached JMS objects related to that configuration. Otherwise it will
+  execute the JNDI lookup and open a new connection. In that case the connection will be closed
+  immediately after sending the message.
+  
 * {Content type detection}
 
   [Incoming requests]