From do-not-reply at jboss.org Tue Mar 29 22:48:02 2011
Content-Type: multipart/mixed; boundary="===============6810379213598288716=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: hornetq-commits at lists.jboss.org
Subject: [hornetq-commits] JBoss hornetq SVN: r10415 -
trunk/hornetq-rest/docbook/reference/en.
Date: Tue, 29 Mar 2011 22:48:02 -0400
Message-ID: <201103300248.p2U2m29Y029547@svn01.web.mwc.hst.phx2.redhat.com>
--===============6810379213598288716==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: bill.burke(a)jboss.com
Date: 2011-03-29 22:48:02 -0400 (Tue, 29 Mar 2011)
New Revision: 10415
Modified:
trunk/hornetq-rest/docbook/reference/en/master.xml
Log:
blah
Modified: trunk/hornetq-rest/docbook/reference/en/master.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/hornetq-rest/docbook/reference/en/master.xml 2011-03-30 00:38:59 =
UTC (rev 10414)
+++ trunk/hornetq-rest/docbook/reference/en/master.xml 2011-03-30 02:48:02 =
UTC (rev 10415)
@@ -5,7 +5,7 @@
HornetQ REST Interface
=
- 2.2.0
+ 2.2.2
=
@@ -307,6 +307,7 @@
<dups-ok>true</dups-ok>
<topic-push-store-dir>topic-push-store</topic-push-store-dir&g=
t;
<queue-push-store-dir>queue-push-store</queue-push-store-dir&g=
t;
+ <producer-time-to-live>0</producer-time-to-live>
<producer-session-pool-size>10</producer-session-pool-size>
<session-timeout-task-interval>1</session-timeout-task-interva=
l>
<consumer-session-timeout-seconds>300</consumer-session-timeou=
t-seconds>
@@ -388,6 +389,15 @@
=
+ producer-time-to-live
+
+
+ Default time to live for posted messages. Default is no
+ ttl.
+
+
+
+
session-timeout-task-interval
=
@@ -809,9 +819,19 @@
</order>
-
- Expiration and Priority
- You can set he expiration and the priority of the message in th=
e queue or topic by setting an additional query parameter. The ex=
piration query parameter is an integer expressing the time in mil=
liseconds until the message should be expired. The priority is another query parameter with an integer value between 0 and 9 expre=
ssing the priority of the message. i.e.:
+
+
+ TTL, Expiration and Priority
+
+ You can set the time to live, expiration, and/or the priority =
of
+ the message in the queue or topic by setting an additional query
+ parameter. The expiration query parameter is an l=
ong
+ specify the time in milliseconds since epoch (a long date). The
+ ttl query parameter is a time in milliseconds you
+ want the message active. The priority is another
+ query parameter with an integer value between 0 and 9 expressing the
+ priority of the message. i.e.:
+
POST /queues/jms.queue.bar/create?expiration=3D30000=
&priority=3D3
Host: example.com
Content-Type: application/xml
@@ -822,7 +842,7 @@
<cost>$199.99</cost>
</order>
-
+
=
@@ -884,6 +904,7 @@
the server. Only usable on topics.
+
selector
=
@@ -894,6 +915,24 @@
charactor is converted to a '$'.
+
+
+ idle-timeout
+
+
+ For a topic subscription, idle time in milliseconds in whi=
ch
+ the consumer connections will be closed if idle.
+
+
+
+
+ delete-when-idle
+
+
+ Boolean value, If true, a topic subscription will be delet=
ed
+ (even if it is durable) when an the idle timeout is reached.
+
+
=
@@ -1509,6 +1548,9 @@
]]>
</selector>
<link rel=3D"push" href=3D"http://somewhere.com" type=3D"application=
/json" method=3D"PUT"/>
+ <maxRetries>5</maxRetries>
+ <retryWaitMillis>1000</retryWaitMillis>
+ <disableOnFailure>true</disableOnFailure>
</push-registration>
=
@@ -1525,6 +1567,19 @@
JMS message selector. You should enclose it within CDATA blocks as s=
ome
of the selector characters are illegal XML.
=
+ The maxRetries element specifies how many t=
imes
+ a the server will try to push a message to a URL if there is a
+ connection failure.
+
+ The retryWaitMillis element specifies how l=
ong
+ to wait before performing a retry.
+
+ The disableOnFailure element, if set to tru=
e,
+ will disable the registration if all retries have failed. It will not
+ disable the connection on non-connection-failure issues (like a bad
+ request for instance). In these cases, the dead letter queue logic of
+ HornetQ will take over.
+
The link element specifies the basis of the
interaction. The href attribute contains the URL =
you
want to interact with. It is the only required attribute. The
@@ -1595,7 +1650,7 @@
=
The push XML for a topic is the same except the root element is
push-topic-registration. (Also remember the selector
- element is optional). The rest of the document is the same. Here's =
an
+ element is optional). The rest of the document is the same. Here's an
example of a template registration:
=
<push-topic-registration>
--===============6810379213598288716==--