Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-1704

Service w/JMS transport should support non-jndi destinationName and destinationStyle

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.1, 2.0.7
    • Fix Version/s: 2.0.9, 2.1.3
    • Component/s: Transports
    • Labels:
      None

      Description

      I have a service configured with a JMS transport that references a dynamic queue for its destination. The JMS broker I am using does not support jndi lookups on dynamic queues but instead returns an error when such an attempt is made. OTOH, the ActiveMQ JMS broker automatically creates a dynamic queue if a jndi lookup on it is performed and the dynamic queue does not yet exist.

      So, in order for CXF to support dynamic queues on non-ActiveMQ brokers, I suggest it be enhanced to resolve non-jndi destination names. This is similar to the support in Spring JMS for a DynamicDestinationResolver in addition to the JndiDestinationResolver.

      An attribute, jmsProviderDestinationName, might be added to the http://cxf.apache.org/schemas/wsdl/jms.xsd AddressType, to capture a non-jndi destinationName. See servicemix-jms (http://servicemix.apache.org/servicemix-jms.html) for information regarding how it distinguishes between a jndiDestinationName vs. a jmsProviderDestinationName.

      See http://www.nabble.com/CXF-Service-w-JMS-Transport---non-ActiveMQ-Dynamic-Queue-td18479791.html for additional details.

        Attachments

          Activity

            People

            • Assignee:
              ulhasbhole Ulhas Bhole
              Reporter:
              rgavlin Ron Gavlin
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: