[jira] [Closed] (AMQCPP-477) Can't specify empty values in URIs

2013-04-26 Thread Timothy Bish (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMQCPP-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish closed AMQCPP-477.
---

Resolution: Not A Problem

All options require a value otherwise the URI is invalid, plus you definitely 
need a topic and queue prefix or things will end badly. 

 Can't specify empty values in URIs
 --

 Key: AMQCPP-477
 URL: https://issues.apache.org/jira/browse/AMQCPP-477
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: Transports
Affects Versions: 3.6.0
Reporter: Valeriy V. Argunov
Assignee: Timothy Bish

 Can't specify empty values for wireFormat.topicPrefix, wireFormat.queuePrefix 
 etc in URIs because URISupport::parseQuery doesn't support this.
 It can't parse such URI correctly:
 tcp://10.0.0.1:333?wireFormat=stompwireFormat.topicPrefix=wireFormat.queuePrefix=
 I've fixed this by the following code in URISupport::parseQuery:
 int tokensCount = tokenizer.countTokens();
 if (tokensCount != 2  tokensCount != 1) {
 throw IllegalArgumentException(__FILE__, __LINE__, 
 URISupport::parseQuery - Invalid URI Option.);
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Closed] (AMQCPP-477) Can't specify empty values in URIs

2013-04-26 Thread Timothy Bish (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMQCPP-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish closed AMQCPP-477.
---

Resolution: Won't Fix

 Can't specify empty values in URIs
 --

 Key: AMQCPP-477
 URL: https://issues.apache.org/jira/browse/AMQCPP-477
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: Transports
Affects Versions: 3.6.0
Reporter: Valeriy V. Argunov
Assignee: Timothy Bish

 Can't specify empty values for wireFormat.topicPrefix, wireFormat.queuePrefix 
 etc in URIs because URISupport::parseQuery doesn't support this.
 It can't parse such URI correctly:
 tcp://10.0.0.1:333?wireFormat=stompwireFormat.topicPrefix=wireFormat.queuePrefix=
 I've fixed this by the following code in URISupport::parseQuery:
 int tokensCount = tokenizer.countTokens();
 if (tokensCount != 2  tokensCount != 1) {
 throw IllegalArgumentException(__FILE__, __LINE__, 
 URISupport::parseQuery - Invalid URI Option.);
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira