You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Ron Gavlin (JIRA)" <ji...@apache.org> on 2008/07/17 07:05:31 UTC
[jira] Created: (CXF-1704) Service w/JMS transport should support
non-jndi destinationName and destinationStyle
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.
[jira] Assigned: (CXF-1704) Service w/JMS transport should support
non-jndi destinationName and destinationStyle
Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ulhas Bhole reassigned CXF-1704:
--------------------------------
Assignee: Ulhas Bhole
> 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.1.1, 2.0.7
> Reporter: Ron Gavlin
> Assignee: Ulhas Bhole
>
> 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.
[jira] Commented: (CXF-1704) Service w/JMS transport should support
non-jndi destinationName and destinationStyle
Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616411#action_12616411 ]
Ulhas Bhole commented on CXF-1704:
----------------------------------
Sending .
Sending rt/transports/jms/src/main/java/org/apache/cxf/transport/jms/JMSProviderHub.java
Sending rt/transports/jms/src/main/java/org/apache/cxf/transport/jms/JMSTransportBase.java
Sending rt/transports/jms/src/main/resources/META-INF/cxf/extensions.xml
Sending rt/transports/jms/src/main/resources/schemas/wsdl/jms.xsd
Sending systests/src/test/java/org/apache/cxf/systest/jms/GreeterByteMessageImpl.java
Sending systests/src/test/java/org/apache/cxf/systest/jms/GreeterImplDoc.java
Adding systests/src/test/java/org/apache/cxf/systest/jms/GreeterImplDocBase.java
Sending systests/src/test/java/org/apache/cxf/systest/jms/GreeterImplTwoWayJMS.java
Sending systests/src/test/java/org/apache/cxf/systest/jms/JMSClientServerTest.java
Adding systests/src/test/java/org/apache/cxf/systest/jms/JmsDestPubSubImpl.java
Sending systests/src/test/java/org/apache/cxf/systest/jms/Server.java
Adding systests/src/test/java/org/apache/cxf/systest/jms/SoapService6SoapPort6Impl.java
Adding systests/src/test/java/org/apache/cxf/systest/jms/TwoWayJMSImplBase.java
Sending testutils/src/main/resources/wsdl/hello_world_doc_lit.wsdl
Sending testutils/src/main/resources/wsdl/jms_test.wsdl
Transmitting file data ...........
Committed revision 679316.
> 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.1.1, 2.0.7
> Reporter: Ron Gavlin
> Assignee: Ulhas Bhole
>
> 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.
[jira] Resolved: (CXF-1704) Service w/JMS transport should support
non-jndi destinationName and destinationStyle
Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ulhas Bhole resolved CXF-1704.
------------------------------
Resolution: Fixed
> 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.1.1, 2.0.7
> Reporter: Ron Gavlin
> Assignee: Ulhas Bhole
>
> 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.