[AMQNET-261] NMS URI handling in URISupport needs improvement.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.4.0
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 12/Jul/10 20:39
• Updated: 11/Aug/10 22:15
• Resolved: 16/Jul/10 14:19

Description

The URI handling in NMS that allows for composite URIs and for setting options via the URI needs some work.

1. When setting options for the connection when a Failover URI is specified you receive and exception because the options aren't filter out based on the prefix, so for instance a value of connection=asyncSend=true will cause an exception in the failover URI case but not in a plain TCP uri case. Example: The following URI additional test case added to NMSConnectionFactoryTest should work, but it gives an exception.

		[Row("activemq:failover:(tcp://${activemqhost}:61616)?connection.asyncSend=true")]

2. Those referring to the AMQ docs will assume that URIs like the one's below should work but will get an exception instead.

    failover://(tcp://localhost:61616,tcp://remotehost:61616)?initialReconnectDelay=100
    failover://tcp://primary:61616