[
https://issues.apache.org/activemq/browse/AMQCPP-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39150
]
Nathan Mittler commented on AMQCPP-115:
---------------------------------------
Looks like the only place that Properties is used in CMS is in the Destination
API, where it is read-only. Perhaps we could change the getProperties method
to simply return a std::vector< std::pair< std::string, std::string > >?
It might not be as nice from the user perspective, but it might be an easy way
to eliminate Properties as a dependency of CMS.
What do u guys think?
> Change build to create dynamic libraries
> ----------------------------------------
>
> Key: AMQCPP-115
> URL: https://issues.apache.org/activemq/browse/AMQCPP-115
> Project: ActiveMQ C++ Client
> Issue Type: Task
> Environment: *nix, win32
> Reporter: Nathan Mittler
> Assigned To: Nathan Mittler
> Priority: Minor
> Fix For: 2.1
>
> Attachments: amqcppdllv1.diff, amqcppdllv2.diff, amqcppdllv3.diff
>
>
> Based on a flurry of user requests, we need to add support for generating
> dynamic libraries to our automake scripts and the msvc project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.