[esb-issues] [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.
[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12368947 ]
Mark Little commented on JBESB-646:
-----------------------------------
BTW, this has everything to do with sending and receiving reliably versus unreliably. So
far JMS is our only reliable transport and yet reliability is something we're not
exposing to the end user: it just happens because we've implemented our JMS usage that
way. I'm not suggesting we make this change for 4.2, but in 5.0 (and the original
pre-rosetta architecture) we had an API to sendReliable and sendUnreliable. Then it's
not in the EPR, but in the service contract.
NON_PERSISTENT JMS messaging.
-----------------------------
Key: JBESB-646
URL: http://jira.jboss.com/jira/browse/JBESB-646
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 2
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Critical
Fix For: 4.2
The current classes that deal with sending JMS messages, like JMSCourier, do not specify
a delivery mode when sending messages. The default is then that the messages are sent with
a delivery mode of persistent.
The request (see forum reference) is to be able have the delivery mode configurable so
one can avoid the persisting to stable storage.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira