You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by ch...@apache.org on 2011/06/09 17:28:03 UTC
svn commit: r1133933 -
/activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md
Author: chirino
Date: Thu Jun 9 15:28:02 2011
New Revision: 1133933
URL: http://svn.apache.org/viewvc?rev=1133933&view=rev
Log:
Fix documentation of the add user header element.
Modified:
activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md
Modified: activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md
URL: http://svn.apache.org/viewvc/activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md?rev=1133933&r1=1133932&r2=1133933&view=diff
==============================================================================
--- activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md (original)
+++ activemq/activemq-apollo/trunk/apollo-website/src/documentation/user-manual.md Thu Jun 9 15:28:02 2011
@@ -942,9 +942,9 @@ headers are parsed and interpreted. The
It also supports nested `add_user_header` elements to more finely control how
user headers are added to received STOMP messages. The `add_user_header` element
+should contain the name of the header to set on the STOMP message. It also
supports the following attributes:
-* `name` : The name of the header to set on the STOMP message
* `separator` : If user has multiple principles which match, this separator
will be used to delimit them in the header. If not set, then only the first
matching principle will be set in the header.
@@ -956,8 +956,7 @@ Example:
{pygmentize:: xml}
<connector id="tcp" bind="tcp://0.0.0.0:61613">
<stomp max_header_length="10000">
- <add_user_header name="user" separator=","
- kind="org.apache.activemq.jaas.UserPrincipal" />
+ <add_user_header separator=",">user</add_user_header>
</stomp>
</connector>
{pygmentize}