ReplyDestinationType for JMSEndpoint is not defaulting to queue
---------------------------------------------------------------
Key: TRANSPORTS-26
URL: https://issues.apache.org/jira/browse/TRANSPORTS-26
Project: Axis2 Transports
Issue Type: Bug
Components: JMS
Affects Versions: 1.0.0
Environment: Operating System - Windows XP Professional
Tomcat v6.0.28
IBM Websphere MQ v7.0.1.2
Axis2 v1.5.1
JMS Transport version 1.0.0
Reporter: Rajeev Verma
Priority: Minor
There is a small defect in loadConfiguration method of JMSEndpoint class.
replyDestinationType is not getting defaulted to queue if parameter
transport.jms.ReplyDestinationType is not set in the services.xml.
Parameter replyDestTypeParam =
service.getParameter(JMSConstants.PARAM_REPLY_DEST_TYPE);
if (replyDestTypeParam != null) {
String paramValue = (String) replyDestTypeParam.getValue();
if (JMSConstants.DESTINATION_TYPE_QUEUE.equals(paramValue) ||
JMSConstants.DESTINATION_TYPE_TOPIC.equals(paramValue) ) {
setReplyDestinationType(paramValue);
} else {
throw new AxisFault("Invalid destinaton type value " +
paramValue);
}
} else {
log.debug("JMS reply destination type not given. default queue");
destinationType = JMSConstants.QUEUE;
}
In the last else back it should have been replyDestinationType =
JMSConstants.QUEUE; instead of destinationType = JMSConstants.QUEUE;
Workaround for the issue is to explicitly pass the parameter
transport.jms.ReplyDestinationType in services.xml
--
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: [email protected]
For additional commands, e-mail: [email protected]
