Author: veithen
Date: Wed Apr 15 09:44:02 2009
New Revision: 765097
URL: http://svn.apache.org/viewvc?rev=765097&view=rev
Log:
Added some info about message context properties to the JMS transport docs.
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=765097&r1=765096&r2=765097&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 15
09:44:02 2009
@@ -81,7 +81,9 @@
[<<<transport.jms.CacheLevel>>>]
TODO
-* {JMS connections and message dispatching}
+* {Transport listener}
+
+** {JMS connections and message dispatching}
Every deployed service for which the JMS transport is enabled will be
associated with a
destination (queue or topic) according to the following rules:
@@ -113,7 +115,7 @@
In addition, if the JMS message has a property named <<<SOAPAction>>>, the
value of this property
is interpreted as the SOAP action.
-* {Service configuration}
+** {Service configuration}
[<<<transport.jms.ConnectionFactory>>> (Optional)]
The JMS connection factory definition (from <<<axis2.xml>>>) to be used to
@@ -195,7 +197,17 @@
</service>
+--------------------------------------------+
-* {Endpoint references}
+** {Message context properties for incoming messages}
+
+ For incoming messages, the transport listener will make the following
properties available in
+ the message context:
+
+ [<<<TRANSPORT_HEADERS>>>]
+ This property will contain a map with the JMS message properties.
+
+* {Transport sender}
+
+** {Endpoint references}
Endpoint references for the JMS transport must have the following form:
@@ -248,6 +260,17 @@
execute the JNDI lookup and open a new connection. In that case the
connection will be closed
immediately after sending the message.
+** {Message context properties for outcoming messages}
+
+ For outgoing messages, the transport sender will recognize the following
message context
+ properties:
+
+ [<<<TRANSPORT_HEADERS>>>]
+ The transport expects a map as value for this property. The entries of
this map will be
+ set as properties on the outgoing JMS message.
+
+ Note that all the properties are optional.
+
* {Content type detection}
[Incoming requests]
