You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Dan Becker (JIRA)" <de...@tuscany.apache.org> on 2009/02/24 21:15:01 UTC
[jira] Created: (TUSCANY-2870) JMSBinding should support
non-Boolean delivery modes for binding and operations
JMSBinding should support non-Boolean delivery modes for binding and operations
-------------------------------------------------------------------------------
Key: TUSCANY-2870
URL: https://issues.apache.org/jira/browse/TUSCANY-2870
Project: Tuscany
Issue Type: Improvement
Components: Java SCA JMS Binding Extension
Affects Versions: Java-SCA-1.4
Environment: All
Reporter: Dan Becker
Priority: Minor
The JMS Binding models delivery mode as a Boolean. There are APIs for
public Boolean getOperationJMSDeliveryMode(String opName)
public void setOperationJMSDeliveryMode(String opName, boolean b)
and
public Boolean isdeliveryModePersistent()
public void setJMSDeliveryMode(boolean persistent) {
Currently the Java JMS specification uses ints for these delivery modes and has the following APIs:
public void setDeliveryMode(int deliveryMode) throws JMSException
public int getDeliveryMode() throws JMSException
The deliveryMode int is modeled by javax.jms.DeliveryMode interface with constants for
NON_PERSISTENT
PERSISTENT
Tuscany should use ints instead of booleans.
a) Using DeliveryMode interface constants is more readable.
b) Using DeliveryMode interface constants is more flexible (more possible values)
c) Using DeliveryMode interface cosntants is more expandable. In the future there might be other int values in the interface such as DeliveryMode.DEFAULT or DeliveryMode.BEST_PERFORMANCE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.