[
https://issues.apache.org/activemq/browse/AMQNET-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49924#action_49924
]
Jim Gomes commented on AMQNET-144:
----------------------------------
Apologies for the inconvenience. The intent of the URL being set to
tcp://activemqhost:61616 is to create the situation where the text file does
NOT need to be edited at all. What is intended to be edited is the users local
HOSTS file. On Windows this file is located in
C:\Windows\System32\drivers\etc. If you always run ActiveMQ on the local host,
then add the following line to the HOSTS file:
127.0.0.1 activemqhost
Because I don't run ActiveMQ on my local machine, and I can't guarantee or
force others to do the same, then it is better to create a generically named
host machine and allow each user to resolve that generic name.
This was the intent of the naming inside the configuration file.
> Default broker URL in nmsprovider-test.config should be the default URL of
> the broker, ie localhost:61616
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-144
> URL: https://issues.apache.org/activemq/browse/AMQNET-144
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Environment: All
> Reporter: Yev Bronshteyn
> Assignee: Timothy Bish
>
> It's quite inconvenient to have to edit a text file on each checkout. An
> ideal way of managing the broker URL would be defaulting to
> tcp://localhost:61616 and reading the rest from a special en environment
> variable, let's say ACTIVEMQ_URL. This way, if somone's broker is set up at a
> non-default hostname, the necessary tweak would be specific to that user's
> system, and not to a copy of the source tree. I'd happily volunteer to
> implement the change myself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
