Missing destination type in JMS transport causes an NPE -------------------------------------------------------
Key: TRANSPORTS-48 URL: https://issues.apache.org/jira/browse/TRANSPORTS-48 Project: Axis2 Transports Issue Type: Bug Components: JMS Affects Versions: 1.6.0 Reporter: Vijayaratha Vijayasingam Priority: Critical Attachments: jmstransport.patch When we define an endpoint like[1] and [2] NPE occurs in the 2nd case.. [1]jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.DestinationType=queue [2] jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616 According to the axis2 jms transport guide.[3], if we don't define the destination type in endpoint uri, that will be treated as 'queue', "transport.jms.DestinationType (Optional) The JMS destination type. Accept values 'queue' or 'topic' (default: queue)." Here , i have attached the patch for jms transport module, according to my assumption..please check and commit... [3]http://axis.apache.org/axis2/java/transports/jms.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org