You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2021/07/02 12:40:00 UTC
[jira] [Issue Comment Deleted] (QPIDJMS-542) Support configuring
default ConnectionFactory via the naming provider url property
[ https://issues.apache.org/jira/browse/QPIDJMS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPIDJMS-542:
-----------------------------------
Comment: was deleted
(was: michaelandrepearce commented on pull request #41:
URL: https://github.com/apache/qpid-jms/pull/41#issuecomment-869782641
@gemmellr nice, thanks. obviously im used to artemis release schedules of about 1 every 2 -3 months, but i know i see qpid ones a bit more regular how long roughly till this hits the next release?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
)
> Support configuring default ConnectionFactory via the naming provider url property
> ----------------------------------------------------------------------------------
>
> Key: QPIDJMS-542
> URL: https://issues.apache.org/jira/browse/QPIDJMS-542
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 1.0.0
> Reporter: Michael Andre Pearce
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 1.1.0
>
>
> Both in ActiveMQ OpenWire and ActiveMQ Artemis Core clients with their respective JMS InitialContextFactory implementations it is possible to set the connection url as the naming provider url property directly, creating default connection factories with that connection url.
> This is very convenient as well some third party systems annoyingly have also been built around that, making transition to Qpid JMS client from older ActiveMQ Openwire or Artemis less straightforward where we want to migrate fully to AMQP protocol with the brokers from all systems.
> e.g.
> ActiveMQ 5.x Openwire:
> {code:java}
> java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> java.naming.provider.url=tcp://hostname:61616
> {code}
> ActiveMQ Artemis Core
> {code:java}
> java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory
> java.naming.provider.url=tcp://localhost:5445
> {code}
>
> Intent is to support the same, for qpid-jms.
> e.g.
> {code:java}
> java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
> java.naming.provider.url=amqps://localhost:5672
> {code}
> or
> {code:java}
> java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
> java.naming.provider.url=failover:(amqps://host1:5672,amqps://host2:5672)
> {code}
> Followed by e.g. lookup of the "ConnectionFactory" default factory created on the Context:
> {code:java}
> ConnectionFactory connectionFactory = (ConnectionFactory) context.lookup("ConnectionFactory");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org