We do this using QMF calls... they achieve the same effect as old C++ client libraries
On Tue, Dec 11, 2012 at 1:40 PM, Chuck Rolke <[email protected]> wrote: > Hi, > > In the source tree there is a picture of how the .NET binding fits into > the native C++ messaging world: > qpid/cpp/doc/dev-readme/QPID-Component-README.pdf > > The .NET Binding gives you access to the messaging library but no direct > access to the client library. Going forward the messaging interface will > give you a stable API to use when migrating to future versions Qpid > distributions and AMQP 1.0. > > Some tasks like declaring queues and topics may be done programatically by > using features contained in the addressing syntax. Other management tasks > are done simply and directly using the python script qpid-config. > See http://qpid.apache.org/books/0.18/Programming-In-Apache-Qpid/html/ > > -Chuck > > ----- Original Message ----- > > From: "Wurzinger Peter" <[email protected]> > > To: [email protected] > > Sent: Tuesday, December 11, 2012 6:57:15 AM > > Subject: Question for Client Libraries to declare Queues, add > bindings,... > > > > Hi! > > > > In our company we're using Apache QPID in some of our > > company-internal web-applications (ASP.NET, C#). > > One of them has the job to manage the QPID-Broker running on one of > > our internal servers. > > This is a quite old application and my job is to get it working for > > the newest QPID-Version (0.16), currently we're using QPID 0.6. > > I've managed to run the 0.16 Broker and compile the > > org.apache.qpid.messaging - Assemblies for the applications > > exchanging data using QPID. > > > > My problem now is, that the QPID-managing application uses an > > Assembly called "qpid.client.dll", which provides functionality to > > declare queues, add bindings and so on, but in the newest version of > > QPID I cannot find this Assembly. Is/Are there any replacement/s for > > this Assembly? > > > > Best Regards > > Peter > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
