You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <de...@tuscany.apache.org> on 2009/01/30 15:36:00 UTC
[jira] Assigned: (TUSCANY-2798) Response destination not used in
when JMSReplyTo is absent
[ https://issues.apache.org/jira/browse/TUSCANY-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ant elder reassigned TUSCANY-2798:
----------------------------------
Assignee: ant elder
> Response destination not used in <binding.jms> when JMSReplyTo is absent
> ------------------------------------------------------------------------
>
> Key: TUSCANY-2798
> URL: https://issues.apache.org/jira/browse/TUSCANY-2798
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Reporter: Scott Kurz
> Assignee: ant elder
>
> The OASIS JMS Binding spec makes this clear whereas the OSOA doesn't, but if the JMSReplyTo isn't present on the incoming requestMessage then the response destination should be used.
> Not sure the best place to tweak the code to add this just yet, but you can see in TransportServiceInterceptor what we do today in sca-java-1.x
> public Message invokeResponse(Message msg) {
> ...
> if (requestJMSMsg.getJMSReplyTo() == null) {
> // assume no reply is expected
> if (msg.getBody() != null) {
> logger.log(Level.FINE, "JMS service '" + service.getName() + "' dropped response as request has no replyTo");
> }
> return msg;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.