[esb-issues] [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.
Daniel Bevenius (JIRA)
jira-events at lists.jboss.org
Tue Oct 2 09:27:03 EDT 2007
[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12379889 ]
Daniel Bevenius commented on JBESB-646:
---------------------------------------
> can we do this within the config as originally thought?
Do you mean like Burr suggested:
<jms-bus busid="quickstartGwChannel">
<jms-message-filter
dest-type="QUEUE"
dest-name="queue/quickstart_business_service_Request"
persist="true" <!-- or something like that -->
/>
</jms-bus>
I see no problem with this, the only problem is getting this information to the JMSCourier without going via the JMSEpr.
> 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: Blocker
> Fix For: 4.2.1 IR2
>
>
> 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
More information about the esb-issues
mailing list