You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Joe Luo (JIRA)" <ji...@apache.org> on 2010/01/21 16:56:44 UTC
[jira] Created: (SMXCOMP-702) New JMS Provider endpoint should
allow per message setting of JMSPriority or JMSTimeToLive
New JMS Provider endpoint should allow per message setting of JMSPriority or JMSTimeToLive
------------------------------------------------------------------------------------------
Key: SMXCOMP-702
URL: https://issues.apache.org/activemq/browse/SMXCOMP-702
Project: ServiceMix Components
Issue Type: Improvement
Components: servicemix-jms
Reporter: Joe Luo
Attachments: smx-jms-patch.patch
The new JMS provider endpoint does not allow per message setting of QoS properties such as priority and timeToLive.
When sending a message to destination, the JmsProviderEndpoint invokes "send(Destination dest, MessageCreator message)" on Spring JmsTemplate:
{code}
template.send(dest, new MessageCreator() {
public Message createMessage(Session session) throws JMSException {
return message;
}
});
{code}
Then, the Spring JmsTemplate calls doSend() function:
{code}
protected void doSend(MessageProducer producer, Message message) throws JMSException {
if (isExplicitQosEnabled()) {
producer.send(message, getDeliveryMode(), getPriority(), getTimeToLive());
}
else {
producer.send(message);
}
}
{code}
Basically, the Spring JMSTemplate will override "JMSDeliveryMode", "JMSPriority" and "JMSExpiration" properties that specified on the message.
We should allow per message setting of QoS properties such as priority and timeToLive by the new Jms provider endpoint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-702) New JMS Provider endpoint should
allow per message setting of JMSPriority or JMSTimeToLive
Posted by "Joe Luo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Luo updated SMXCOMP-702:
----------------------------
Attachment: smx-jms-patch.patch
> New JMS Provider endpoint should allow per message setting of JMSPriority or JMSTimeToLive
> ------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-702
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-702
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-jms
> Reporter: Joe Luo
> Attachments: smx-jms-patch.patch
>
>
> The new JMS provider endpoint does not allow per message setting of QoS properties such as priority and timeToLive.
> When sending a message to destination, the JmsProviderEndpoint invokes "send(Destination dest, MessageCreator message)" on Spring JmsTemplate:
> {code}
> template.send(dest, new MessageCreator() {
> public Message createMessage(Session session) throws JMSException {
> return message;
> }
> });
> {code}
> Then, the Spring JmsTemplate calls doSend() function:
> {code}
> protected void doSend(MessageProducer producer, Message message) throws JMSException {
> if (isExplicitQosEnabled()) {
> producer.send(message, getDeliveryMode(), getPriority(), getTimeToLive());
> }
> else {
> producer.send(message);
> }
> }
> {code}
> Basically, the Spring JMSTemplate will override "JMSDeliveryMode", "JMSPriority" and "JMSExpiration" properties that specified on the message.
> We should allow per message setting of QoS properties such as priority and timeToLive by the new Jms provider endpoint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SMXCOMP-702) New JMS Provider endpoint should
allow per message setting of JMSPriority or JMSTimeToLive
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen reassigned SMXCOMP-702:
---------------------------------------
Assignee: Gert Vanthienen (was: Chris Custine)
> New JMS Provider endpoint should allow per message setting of JMSPriority or JMSTimeToLive
> ------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-702
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-702
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-jms
> Reporter: Joe Luo
> Assignee: Gert Vanthienen
> Attachments: smx-jms-patch.patch
>
>
> The new JMS provider endpoint does not allow per message setting of QoS properties such as priority and timeToLive.
> When sending a message to destination, the JmsProviderEndpoint invokes "send(Destination dest, MessageCreator message)" on Spring JmsTemplate:
> {code}
> template.send(dest, new MessageCreator() {
> public Message createMessage(Session session) throws JMSException {
> return message;
> }
> });
> {code}
> Then, the Spring JmsTemplate calls doSend() function:
> {code}
> protected void doSend(MessageProducer producer, Message message) throws JMSException {
> if (isExplicitQosEnabled()) {
> producer.send(message, getDeliveryMode(), getPriority(), getTimeToLive());
> }
> else {
> producer.send(message);
> }
> }
> {code}
> Basically, the Spring JMSTemplate will override "JMSDeliveryMode", "JMSPriority" and "JMSExpiration" properties that specified on the message.
> We should allow per message setting of QoS properties such as priority and timeToLive by the new Jms provider endpoint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SMXCOMP-702) New JMS Provider endpoint should
allow per message setting of JMSPriority or JMSTimeToLive
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Custine reassigned SMXCOMP-702:
-------------------------------------
Assignee: Chris Custine
> New JMS Provider endpoint should allow per message setting of JMSPriority or JMSTimeToLive
> ------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-702
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-702
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-jms
> Reporter: Joe Luo
> Assignee: Chris Custine
> Attachments: smx-jms-patch.patch
>
>
> The new JMS provider endpoint does not allow per message setting of QoS properties such as priority and timeToLive.
> When sending a message to destination, the JmsProviderEndpoint invokes "send(Destination dest, MessageCreator message)" on Spring JmsTemplate:
> {code}
> template.send(dest, new MessageCreator() {
> public Message createMessage(Session session) throws JMSException {
> return message;
> }
> });
> {code}
> Then, the Spring JmsTemplate calls doSend() function:
> {code}
> protected void doSend(MessageProducer producer, Message message) throws JMSException {
> if (isExplicitQosEnabled()) {
> producer.send(message, getDeliveryMode(), getPriority(), getTimeToLive());
> }
> else {
> producer.send(message);
> }
> }
> {code}
> Basically, the Spring JMSTemplate will override "JMSDeliveryMode", "JMSPriority" and "JMSExpiration" properties that specified on the message.
> We should allow per message setting of QoS properties such as priority and timeToLive by the new Jms provider endpoint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMXCOMP-702) New JMS Provider endpoint should
allow per message setting of JMSPriority or JMSTimeToLive
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SMXCOMP-702.
-------------------------------------
Resolution: Fixed
Fix Version/s: servicemix-jms-2010.01
Fixed in http://svn.apache.org/viewvc?view=revision&revision=903130
Thanks to Joe Luo for providing the patch!
> New JMS Provider endpoint should allow per message setting of JMSPriority or JMSTimeToLive
> ------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-702
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-702
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-jms
> Reporter: Joe Luo
> Assignee: Gert Vanthienen
> Fix For: servicemix-jms-2010.01
>
> Attachments: smx-jms-patch.patch
>
>
> The new JMS provider endpoint does not allow per message setting of QoS properties such as priority and timeToLive.
> When sending a message to destination, the JmsProviderEndpoint invokes "send(Destination dest, MessageCreator message)" on Spring JmsTemplate:
> {code}
> template.send(dest, new MessageCreator() {
> public Message createMessage(Session session) throws JMSException {
> return message;
> }
> });
> {code}
> Then, the Spring JmsTemplate calls doSend() function:
> {code}
> protected void doSend(MessageProducer producer, Message message) throws JMSException {
> if (isExplicitQosEnabled()) {
> producer.send(message, getDeliveryMode(), getPriority(), getTimeToLive());
> }
> else {
> producer.send(message);
> }
> }
> {code}
> Basically, the Spring JMSTemplate will override "JMSDeliveryMode", "JMSPriority" and "JMSExpiration" properties that specified on the message.
> We should allow per message setting of QoS properties such as priority and timeToLive by the new Jms provider endpoint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.