RE: (repost) FW: A word of warning: SwiftMQ and Resource providers.

2002-02-20 Thread Ray Harrison
I am using 1.3.1_02 and SwiftMQ 3.0 beta. --- Geoff Soutter [EMAIL PROTECTED] wrote: Hmm. Strange. I'm definitely using 1.5.4, you can see it in the console output I included below. I tried doing an autoupdate and trying it again, made no difference. I even did a recursive diff against

RE: (repost) FW: A word of warning: SwiftMQ and Resource providers.

2002-02-20 Thread Ray Harrison
Also, I just tested the ATM as per Magnus' suggestion and it worked there as well. Have you tried it with SwiftMQ 3.0 (I know they just got rid of their free licenses)? I will try it later with version 2.x. Cheers Ray --- Ray Harrison [EMAIL PROTECTED] wrote: I am using 1.3.1_02 and SwiftMQ

SV: (repost) FW: A word of warning: SwiftMQ and Resource providers.

2002-02-20 Thread Magnus Rydin
For the record, in our tests we were using both 1.3.1_02 and 1.4.0_b92 together with Swift 2.1.3 WR -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] För Ray Harrison Skickat: den 20 februari 2002 13:40 Till: Orion-Interest Ämne: RE: (repost) FW: A word of

(repost) FW: A word of warning: SwiftMQ and Resource providers.

2002-02-19 Thread Geoff Soutter
Argh. Mailing lists that are not reliable annoy the out of me. -Original Message- From: Geoff Soutter [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 19 February 2002 9:32 AM To: 'Orion-Interest' Subject: RE: A word of warning: SwiftMQ and Resource providers. Hi Magnus, All I did was

Re: (repost) FW: A word of warning: SwiftMQ and Resource providers.

2002-02-19 Thread Ray Harrison
Interesting - I *don't* get that error any longer with 1.5.4, though I did with 1.5.3. --- Geoff Soutter [EMAIL PROTECTED] wrote: Argh. Mailing lists that are not reliable annoy the out of me. -Original Message- From: Geoff Soutter [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 19

RE: (repost) FW: A word of warning: SwiftMQ and Resource providers.

2002-02-19 Thread Geoff Soutter
Hmm. Strange. I'm definitely using 1.5.4, you can see it in the console output I included below. I tried doing an autoupdate and trying it again, made no difference. I even did a recursive diff against the .zip version and the autoupdate version and they are identical (despite the fact