Chuck Rolke created QPID-5115:
---------------------------------
Summary: Windows client AMQP 1.0 support should be built in and
not a loadable module
Key: QPID-5115
URL: https://issues.apache.org/jira/browse/QPID-5115
Project: Qpid
Issue Type: Bug
Components: C++ Client
Affects Versions: 0.24
Reporter: Chuck Rolke
Assignee: Chuck Rolke
In order to get a Windows Qpid Messaging client support for AMQP 1.0 the user
must define an environment variable before executing the client program. In
practice this is inconvenient and it may well baffle new users simply trying to
execute HelloWorld.
For example, assume a native windows installation has proton.dll in P:\bin and
the Qpid messaging libraries in Q:\bin.
If the user puts P:\bin and Q:\bin into his path and runs:
{noformat}
helloworld.exe
{noformat}
then no AMQP 1.0 support is available. Simply having qpidc.dll in the user path
is not enough. To get AMQP 1.0 the user must point to the amqpc.dll library:
{noformat}
set QPID_LOAD_MODULE=Q:\bin\qpidc.dll
helloworld.exe
{noformat}
This problem is just as bad for .NET managed code where every application that
wants to inherit use of the client libraries must have this environment
variable set.
The solution proposed here is to simply build amqpc.dll into qpidmessaging.dll
and have support for AMQP 1.0 enabled automatically. AMPQ 1.0 support is
enabled by loading the libraries that are in the user's path.
In order to use AMQP 1.0 users still must specify "{protocol:amqp1.0}" in the
connection options so 1.0 support is not enabled without them knowing about it.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
