[jira] Created: (SM-1015) JMS Expiration value should be configurable

["Arif Mohammed (JIRA)" <ji...@apache.org>]

JMS Expiration value should be configurable
-------------------------------------------

                 Key: SM-1015
                 URL: https://issues.apache.org/activemq/browse/SM-1015
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-jms
            Reporter: Arif Mohammed


JMS Expiration value should be configurable from xbean.xml for both topics and queues, by default this component is assigning a value of 0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SM-1015) JMS Expiration value should be configurable

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39884 ] 

Guillaume Nodet commented on SM-1015:
-------------------------------------

With the 3.2 version, you will be able to specify:

  <jms:provider ... marshaler="#marshaler" />
  <bean id="marshaler" class="org.apache.servicemix.jms.endpoints.DefaultProviderMarshaler">
    <property name="jmsProperties">
      <props>
        <prop key="JMSExpiration">10000</prop>
      </props>
    </property>
  </bean>

or something like that.  Any feedback welcome.

> JMS Expiration value should be configurable
> -------------------------------------------
>
>                 Key: SM-1015
>                 URL: https://issues.apache.org/activemq/browse/SM-1015
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-jms
>            Reporter: Arif Mohammed
>
> JMS Expiration value should be configurable from xbean.xml for both topics and queues, by default this component is assigning a value of 0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.