[jira] [Updated] (AMQCPP-540) Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp
[ https://issues.apache.org/jira/browse/AMQCPP-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valeriy V. Argunov updated AMQCPP-540: -- Patch Info: Patch Available Environment: MSVC2012 Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp -- Key: AMQCPP-540 URL: https://issues.apache.org/jira/browse/AMQCPP-540 Project: ActiveMQ C++ Client Issue Type: Bug Components: Build Support Environment: MSVC2012 Reporter: Valeriy V. Argunov Assignee: Timothy Bish Attachments: AbstractDiscoveryAgent.cpp.patch Here is a patch. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AMQCPP-539) Can't build GIT master on MSVC
[ https://issues.apache.org/jira/browse/AMQCPP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valeriy V. Argunov updated AMQCPP-539: -- Attachment: PlatformDefs.h.patch Patch. Can't build GIT master on MSVC -- Key: AMQCPP-539 URL: https://issues.apache.org/jira/browse/AMQCPP-539 Project: ActiveMQ C++ Client Issue Type: Bug Components: Build Support Environment: MSVC2012 Reporter: Valeriy V. Argunov Assignee: Timothy Bish Attachments: PlatformDefs.h.patch PlatformDefs.h for Windows defines only PLATFORM_DEFAULT_STACK_SIZE, but PlatformThread.cpp tries to use PLATFORM_MIN_STACK_SIZE. Here is a patch. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AMQCPP-539) Can't build GIT master on MSVC
Valeriy V. Argunov created AMQCPP-539: - Summary: Can't build GIT master on MSVC Key: AMQCPP-539 URL: https://issues.apache.org/jira/browse/AMQCPP-539 Project: ActiveMQ C++ Client Issue Type: Bug Components: Build Support Environment: MSVC2012 Reporter: Valeriy V. Argunov Assignee: Timothy Bish Attachments: PlatformDefs.h.patch PlatformDefs.h for Windows defines only PLATFORM_DEFAULT_STACK_SIZE, but PlatformThread.cpp tries to use PLATFORM_MIN_STACK_SIZE. Here is a patch. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AMQCPP-540) Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp
Valeriy V. Argunov created AMQCPP-540: - Summary: Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp Key: AMQCPP-540 URL: https://issues.apache.org/jira/browse/AMQCPP-540 Project: ActiveMQ C++ Client Issue Type: Bug Components: Build Support Reporter: Valeriy V. Argunov Assignee: Timothy Bish Attachments: AbstractDiscoveryAgent.cpp.patch Here is a patch. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AMQCPP-540) Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp
[ https://issues.apache.org/jira/browse/AMQCPP-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valeriy V. Argunov updated AMQCPP-540: -- Attachment: AbstractDiscoveryAgent.cpp.patch Patch. Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp -- Key: AMQCPP-540 URL: https://issues.apache.org/jira/browse/AMQCPP-540 Project: ActiveMQ C++ Client Issue Type: Bug Components: Build Support Reporter: Valeriy V. Argunov Assignee: Timothy Bish Attachments: AbstractDiscoveryAgent.cpp.patch Here is a patch. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (AMQCPP-478) Can't specify empty prefixes for the STOMP queues/topics
[ https://issues.apache.org/jira/browse/AMQCPP-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valeriy V. Argunov reopened AMQCPP-478: --- So it is impossible to use ActiveMQ STOMP client with servers other than ActiveMQ server. Can't specify empty prefixes for the STOMP queues/topics Key: AMQCPP-478 URL: https://issues.apache.org/jira/browse/AMQCPP-478 Project: ActiveMQ C++ Client Issue Type: Bug Components: Transports Affects Versions: 3.6.0 Reporter: Valeriy V. Argunov Assignee: Timothy Bish ActiveMQ-CPP uses prefixes for STOMP queues/topics (defaults are /topic/, /queue/ etc). STOMP specification (http://stomp.github.io/stomp-specification-1.2.html) says that queues/topics names are not required to contain any special prefixes: (from the SEND sample) This sends a message to a destination named /queue/a. Note that STOMP treats this destination as an opaque string and no delivery semantics are assumed by the name of a destination. But if the prefix is not required for me, I can't specify empty string (here was a bug https://issues.apache.org/jira/browse/AMQCPP-477). ActiveMQ-CPP doesn't allow to remove prefixes at all. -- 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] [Created] (AMQCPP-477) Can't specify empty values in URIs
Valeriy V. Argunov created AMQCPP-477:
-
Summary: 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] [Commented] (AMQCPP-477) Can't specify empty values in URIs
[
https://issues.apache.org/jira/browse/AMQCPP-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642953#comment-13642953
]
Valeriy V. Argunov commented on AMQCPP-477:
---
But all applications that use URIs allow empty values for parameters in the
query string. Also see http://en.wikipedia.org/wiki/Query_string
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] [Reopened] (AMQCPP-477) Can't specify empty values in URIs
[
https://issues.apache.org/jira/browse/AMQCPP-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valeriy V. Argunov reopened AMQCPP-477:
---
The issue is still here.
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] [Created] (AMQCPP-478) Can't specify empty prefixes for the STOMP queues/topics
Valeriy V. Argunov created AMQCPP-478: - Summary: Can't specify empty prefixes for the STOMP queues/topics Key: AMQCPP-478 URL: https://issues.apache.org/jira/browse/AMQCPP-478 Project: ActiveMQ C++ Client Issue Type: Bug Components: Transports Affects Versions: 3.6.0 Reporter: Valeriy V. Argunov Assignee: Timothy Bish ActiveMQ-CPP uses prefixes for STOMP queues/topics (defaults are /topic/, /queue/ etc). STOMP specification (http://stomp.github.io/stomp-specification-1.2.html) says that queues/topics names are not required to contain any special prefixes: (from the SEND sample) This sends a message to a destination named /queue/a. Note that STOMP treats this destination as an opaque string and no delivery semantics are assumed by the name of a destination. But if the prefix is not required for me, I can't specify empty string (here was a bug https://issues.apache.org/jira/browse/AMQCPP-477). ActiveMQ-CPP doesn't allow to remove prefixes at all. -- 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
