On Thu, 2010-01-07 at 15:11 -0800, Jim Lloyd wrote: > Whoops! Sorry, I meant to hit save and not send, since I suddenly realized > what might be the cause of my problem. And indeed, I was right, so I no > longer need assistance. But thanks anyway for replying quickly! > > My problem was indeed related to initializing the library, and I had figured > out that I needed to do so from looking at the sample apps. My code was > compiling but not linking. It turns out that I had a subtle error in my > build system and was still linking against old libraries. > > I seem to recall that there was some kind of document describing other > changes that may be necessary in upgrading from 2.x to 3.x, but if there is > I haven't been able to find it. Is there one? > > Jim
There's no upgrade guide unfortunately but there isn't to much that should bite you on the CMS API other than some changes in the Message classes that dictate when certain exceptions are thrown, see the API documentation its pretty good. The examples show the use of the Library init and cleanup. If you get stuck just post a question to the list and we can work through it. Regards Tim. > > On Thu, Jan 7, 2010 at 2:36 PM, Timothy Bish <tabish...@gmail.com> wrote: > > > On Thu, 2010-01-07 at 14:27 -0800, Jim Lloyd wrote: > > > I'm finally upgrading some applications to use activemq-cpp 3.1.1. We had > > > been using 2.2.6 > > > > Great, let us know how it goes, lots of new features in there. > > > > Make sure you take a look at the sample apps for some hints on the > > changes, you need to initialize and uninitialize the library now, FYI. > > > > Regards > > Tim. > > > > > > > > -- > > Tim Bish > > http://fusesource.com > > http://timbish.blogspot.com/ > > > > > > > > -- Tim Bish http://fusesource.com http://timbish.blogspot.com/
