cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Gavlin (JIRA)" <j...@apache.org>
Subject [jira] Created: (CXF-1704) Service w/JMS transport should support non-jndi destinationName and destinationStyle
Date Thu, 17 Jul 2008 05:05:31 GMT
Service w/JMS transport should support non-jndi destinationName and destinationStyle
------------------------------------------------------------------------------------

                 Key: CXF-1704
                 URL: https://issues.apache.org/jira/browse/CXF-1704
             Project: CXF
          Issue Type: New Feature
          Components: Transports
    Affects Versions: 2.0.7, 2.1.1
            Reporter: Ron Gavlin


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.


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


Mime
View raw message