[
https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291144#comment-13291144
]
Jim Gomes commented on AMQNET-387:
----------------------------------
When you program to the Apache.NMS.dll, it uses a generic API that is common
across all JMS providers. The provider to use is specified in the connection
URL. For example, "activemq:tcp://activemqhost:61616". By parsing the URL,
the Apache.NMS.dll recognizes the leading "activemq:" provider and will load
the Apache.NMS.ActiveMQ.dll assembly. If the URL were
"stomp:tcp://activemqhost:61619", then the Apache.NMS.Stomp.dll assembly would
be loaded and used. This is the basic dynamic loading strategy that is
employed.
> no iconnectionfactory implementation found for connection uri
> -------------------------------------------------------------
>
> Key: AMQNET-387
> URL: https://issues.apache.org/jira/browse/AMQNET-387
> Project: ActiveMQ .Net
> Issue Type: Bug
> Reporter: Tamilmaran
> Assignee: Jim Gomes
>
> I'm facing the "no iconnectionfactory implementation found for connection
> uri" issue on the client system.The server side which has the broker into it,
> is running perfectly for topic/queue pub/sub.But the client is not working.
> I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this
> case, How to get rid of this issue?
--
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
