You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Greg Dritschler (JIRA)" <de...@tuscany.apache.org> on 2009/02/17 23:54:59 UTC
[jira] Created: (TUSCANY-2857) Correct handling of JMSDeliveryMode
and JMSPriority
Correct handling of JMSDeliveryMode and JMSPriority
---------------------------------------------------
Key: TUSCANY-2857
URL: https://issues.apache.org/jira/browse/TUSCANY-2857
Project: Tuscany
Issue Type: Bug
Components: Java SCA JMS Binding Extension
Reporter: Greg Dritschler
Priority: Minor
I've noticed that JMSHeaderReferencePolicyInterceptor and TransportServiceInterceptor set the JMSDeliveryMode and JMSPriority headers in the request and response JMS messages respectively before the messages are sent. I am under the impression that the JMS API requires these header values to be set via the MessageProducer interface. The values in the Message are ignored.
See Table 31-1 here: http://docs.sun.com/app/docs/doc/819-3669/bnceh?l=ja&a=view
This issue was discussed on dev list on January 20, 2009 and it was agreed this is a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2857) Correct handling of JMSDeliveryMode
and JMSPriority
Posted by "Dan Becker (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Becker resolved TUSCANY-2857.
---------------------------------
Resolution: Fixed
Fix Version/s: Java-SCA-Next
Completed in branch 1.x: At revision: 747867
> Correct handling of JMSDeliveryMode and JMSPriority
> ---------------------------------------------------
>
> Key: TUSCANY-2857
> URL: https://issues.apache.org/jira/browse/TUSCANY-2857
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Reporter: Greg Dritschler
> Assignee: Dan Becker
> Priority: Minor
> Fix For: Java-SCA-Next
>
>
> I've noticed that JMSHeaderReferencePolicyInterceptor and TransportServiceInterceptor set the JMSDeliveryMode and JMSPriority headers in the request and response JMS messages respectively before the messages are sent. I am under the impression that the JMS API requires these header values to be set via the MessageProducer interface. The values in the Message are ignored.
> See Table 31-1 here: http://docs.sun.com/app/docs/doc/819-3669/bnceh?l=ja&a=view
> This issue was discussed on dev list on January 20, 2009 and it was agreed this is a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2857) Correct handling of JMSDeliveryMode
and JMSPriority
Posted by "Dan Becker (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Becker reassigned TUSCANY-2857:
-----------------------------------
Assignee: Dan Becker
> Correct handling of JMSDeliveryMode and JMSPriority
> ---------------------------------------------------
>
> Key: TUSCANY-2857
> URL: https://issues.apache.org/jira/browse/TUSCANY-2857
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Reporter: Greg Dritschler
> Assignee: Dan Becker
> Priority: Minor
>
> I've noticed that JMSHeaderReferencePolicyInterceptor and TransportServiceInterceptor set the JMSDeliveryMode and JMSPriority headers in the request and response JMS messages respectively before the messages are sent. I am under the impression that the JMS API requires these header values to be set via the MessageProducer interface. The values in the Message are ignored.
> See Table 31-1 here: http://docs.sun.com/app/docs/doc/819-3669/bnceh?l=ja&a=view
> This issue was discussed on dev list on January 20, 2009 and it was agreed this is a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.