[
https://issues.apache.org/jira/browse/QPIDJMS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264873#comment-15264873
]
ASF subversion and git services commented on QPIDJMS-131:
---------------------------------------------------------
Commit bac662d540ab51e418ef2b328c56507d2f9f13cb in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=bac662d ]
https://issues.apache.org/jira/browse/QPIDJMS-131
Initial pass of addition of JmsPresettlePolicy to allow finer control
over presettlement in the JMS client.
> Provide for finer grained control over sending of messages as presettled.
> -------------------------------------------------------------------------
>
> Key: QPIDJMS-131
> URL: https://issues.apache.org/jira/browse/QPIDJMS-131
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.6.0
> Reporter: Timothy Bish
>
> Provider more options for when a message can be sent presettled or not.
> Cases where it makes sense to allow for presettle sends are messages sent as
> non-persistent or messages sent inside a transaction where the transaction
> boundary can provide the sync point for batch send success or failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
