axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Moved: (TRANSPORTS-14) JMS Transport Uses Temporary Topics for replyDestinationType, irrespective of transport.jms.ReplyDestinationType Value
Date Wed, 25 Aug 2010 18:24:15 GMT

     [ https://issues.apache.org/jira/browse/TRANSPORTS-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Veithen moved AXIS2-4499 to TRANSPORTS-14:
--------------------------------------------------

              Project: Axis2 Transports  (was: Axis2)
                  Key: TRANSPORTS-14  (was: AXIS2-4499)
    Affects Version/s: 1.0.0
                           (was: 1.5)
          Component/s: JMS
                           (was: transports)

> JMS Transport Uses Temporary Topics for replyDestinationType, irrespective of transport.jms.ReplyDestinationType
Value
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TRANSPORTS-14
>                 URL: https://issues.apache.org/jira/browse/TRANSPORTS-14
>             Project: Axis2 Transports
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 1.0.0
>         Environment: - Axis2 1.5
> - axis2-transport-jms-1.0-SNAPSHOT.jar
> - axis2-transport-base-1.0-SNAPSHOT.jar
>            Reporter: Curtis Ling
>
> Using the 1.0-SNAPSHOT jars from https://repository.apache.org/index.html#view-repositories;snapshots-group
> Using TIBCO BusinessWorks as a soap server, and a pojo java client.  TIBCO BusinessWorks
is not able to return a reply to a temporary topic, and so expects the replyTo destination
to be a temporary queue.
> When we set the replyDestinationType to "queue" (both in the endpoint URL and the axis2.xml
file), the jms transport ignores it and uses a temporary topic.
> We've added some debug statements to the source code to ensure the issue wasn't configuration
related.  We can see that the replyDestinationType is "queue", but createTemporaryDestination()
in JMSUtils.java doesn't respect the property.
> As a suggestion, it might make sense for that method to examine the property, and instantiate
a new session (a QueueSession, in this case) if one is required.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message