Hi Steve, Is it possible to use Messaging api to have the same behavior like JMS. i.e. I would like to set a message listener at my receiver (I don't see any sample on this, with the messaging api) and for the patern publish/subscribe, can we use the messaging api, or client api (all sample for the pub/sub are done with client api, isn't it ?)
Thanks for your help best regards 2013/6/10 Steve Huston <[email protected]> > Ok great. Thanks for letting us know. > > Steve Huston > (sent from my iPhone - please excuse brevity and typos) > > On Jun 10, 2013, at 6:35 AM, "Xavier Millieret" < > [email protected]> wrote: > > > Hi Steve, > > > > I found the pb, I used the 3.3 python version instead of 2.5.2,. > > it's work fine. > > > > Thanks > > > > > > 2013/6/7 Steve Huston <[email protected]> > > > >> I believe Robbie is away for a time - what type of problem are you > having > >> on Windows? > >> > >> -Steve > >> > >>> -----Original Message----- > >>> From: Xavier Millieret [mailto:[email protected]] > >>> Sent: Friday, June 07, 2013 9:09 AM > >>> To: [email protected] > >>> Subject: Re: Qpid in OSGI > >>> > >>> Hi Robbie, > >>> > >>> I have some problem to generate qpid (c) library for windows, could you > >> help > >>> me please > >>> > >>> > >>> 2013/5/14 Robbie Gemmell <[email protected]> > >>> > >>>> Hi Xavier, > >>>> > >>>> It isn't something I have familiarity with I'm afraid. That said, > >>>> based on the things you have mentioned so far though I would note some > >>>> points: there is a 0.20 based version of the servicemix qpid bundle > >>>> you used, the client no longer depends on Mina or Commons Collections > >>>> (snce 0.14 I think) , and I'm not sure it ever depended on xstream. > >>>> > >>>> Robbie > >>>> > >>>> On 14 May 2013 14:54, Xavier Millieret > >>>> <[email protected] > >>>>> wrote: > >>>> > >>>>> Hi Robbie, > >>>>> > >>>>> Thank you for your reply, but for a qpid client in java and in OSGI > >>>>> platform, could you send me all bundles, that I can use. > >>>>> > >>>>> > >>>>> regards > >>>>> > >>>>> > >>>>> 2013/5/14 Robbie Gemmell <[email protected]> > >>>>> > >>>>>> Hi Xavier, > >>>>>> > >>>>>> I'm afraid I couldn't have been much help with your actual > >>>>>> request, > >>>>> though > >>>>>> it seems like you have got something working, however I did note > >>>>>> that > >>>> the > >>>>>> version of the client you referenced below is around 5 years old, > >>>>>> being from the M2(/0.2) stream some time in 2008. I would > >>>>>> recommend you > >>>> upgrade > >>>>>> to a newer release; the latest is currently 0.20 with 0.22 due out > >>>>>> in > >>>> the > >>>>>> next couple of weeks. > >>>>>> > >>>>>> Robbie > >>>>>> > >>>>>> On 10 May 2013 12:29, Xavier Millieret < > >>>> [email protected] > >>>>>>> wrote: > >>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> I am starting with Qpid, in OSGI. > >>>>>>> when I try to have a connection through jndi like: > >>>>>>> > >>>>>>> Hashtable<String, String> env = new Hashtable<String, String>(); > >>>>>>> env.put(Context.PROVIDER_URL, "qpidConnection.properties"); > >>> env.put(Context.INITIAL_CONTEXT_FACTORY,"org.apache.qpid.jndi.Properti > >>>> esFileInitialContextFactory"); > >>>>>>> > >>>>>>> Context context = new InitialContext(env); ConnectionFactory > >>>>>>> connectionFactory = (ConnectionFactory) > >>>>>>> context.lookup("localhost"); > >>>>>>> > >>>>>>> I have the following error: > >>>>>>> > >>>>>>> javax.naming.NoInitialContextException: Cannot instantiate > >> class: > >>>>>>> org.apache.qpid.jndi.PropertiesFileInitialContextFactory [Root > >>>>> exception > >>>>>> is > >>>>>>> java.lang.ClassNotFoundException: > >>>>>>> org.apache.qpid.jndi.PropertiesFileInitialContextFactory] > >>>>>>> > >>>>>>> I try to use following bundles: > >>>>>>> org.apache.servicemix.bundles.qpid-1.0-incubating-M2.1_1.jar > >>>>>>> > >>>>>>> depends on: > >>>>>>> org.apache.servicemix.bundles.commons-collections-3.2.1_1.jar > >>>>>>> org.apache.servicemix.bundles.mina-1.1.7_3.jar > >>>>>>> > >>>>>>> someone could help me please. > >>>>>>> > >>>>>>> Thank you > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
