Hi Ranjith,
Thanks again for reply.

I just did that. I downloaded Java broker and example source.
(https://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/example/)

build.xml in example source refers to module.xml which is outside example
directory pointed here. So i think just checking out example code wont
work...Please correct me if i am missing something.

Thanks,
Jigar


On Thu, Feb 2, 2012 at 9:42 PM, Rajith Attapattu [via Qpid] <
[email protected]> wrote:

> Hi Jigar,
>
> I'm sorry to hear that you had trouble with running the examples.
> I just checked and I can easily run the Hello.java, Drain and Spout by
> setting the classpath properly.
>
> I simply checked out the source (you can also download the released
> binaries for java, the c++ broker needs to be built from source) and
> then ran "ant build".
> Once I did that I added the jars in build/lib into my classpath and I
> was able to run the examples easily.
>
> The following (Hello.java) illustrates how to send and receive a
> message from an exchange.
>
> http://qpid.apache.org/books/0.14/Programming-In-Apache-Qpid/html/ch03.html#id551166
>
> Do you have any suggestions on what we could do to improve the examples ?
> And what do you think we could add in the docs to make it easy ? ex
> what info do you think is missing ?
>
> As explained in the doc the address syntax is the same for all clients.
> While the documentation certainly needs some improvement I believe it
> does explain the basics of addressing.
> Would it be better if there were more example address strings ?
>
> Could you please explain what you are trying to do? I could then
> provide you with some example address strings that will do what you
> want.
>
> Regards,
>
> Rajith
>
> On Thu, Feb 2, 2012 at 8:34 AM, jigarshaha <[hidden 
> email]<http://user/SendEmail.jtp?type=node&node=7247428&i=0>>
> wrote:
>
> >  Hi Rajith,
> > Thanks for your reply. I did go through tutorials you pointed earlier.
> But
> > these tutorial are more confusing.
> >
> > With absolutely no offense to open source community,
> >
> > Examples referred here do not run. they refer to some exchange but when
> you
> > have JMS console, data is going to temporary queue only.
> >
> > Other spout and drain samples too fail at its best. Still digging
> through
> > them.
> >
> > Concept of address is also too confusing with respect to JMS.
> > And at last Getting Started hardly gets me started on anything.
> >
> > Getting started guide is common for java/C++ and other clients, makes it
> > more confusing.
> >
> > For Sample, c++ and other client have different api. For creating queue
> > they use different syntax. there is nothing there in JMS. Look at what
> has
> > been explained in JMS tutorial. Its all half way.
> >
> > Checkout svn code for example when i call it it does not build. Its
> > expecting whole qpid source.
> >
> > Sorry if i sound harsh, but really i look at docs in more details b4
> > posting on list. (Working on this since past whole week without any
> success)
> >
> > Though i am new to qpid, Have worked on JMS for long. Its just lots of
> > headache to get this working...looking for alternative.
> >
> > Thanks,
> > Jigar
> >
> > On Wed, Feb 1, 2012 at 12:29 AM, Rajith Attapattu [via Qpid] <
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=7247428&i=1>>
> wrote:
> >
> >> On Mon, Jan 30, 2012 at 9:29 AM, jigarshaha <[hidden email]<
> http://user/SendEmail.jtp?type=node&node=7240839&i=0>>
> >> wrote:
> >> > Hi,
> >> > I am very new to qpid. I am trying to configure producer which
> creates
> >> > message with specific type. and puts in exchange, which hosts
> multiple
> >> queue
> >> >
> >> > 1. What exchange-queue mapping is for ? How do i configure Message so
> >> that
> >> > its directed to specific queue in a exchange.
> >>
> >> Have you looked at the examples ? and have you read the docs there ?
> >>
> >>
> http://qpid.apache.org/books/0.14/Programming-In-Apache-Qpid/html/index.html
> >>
> >> The address syntax tells the producer which what exchange/routing key
> >> to use when sending the messages.
> >> The exchange in the broker then decides which queue it goes to based
> >> on the routing key (for the most part)
> >>
> >> >
> >> > 2. in JMS there is nothing like exchange. How this mapping works ?
> >>
> >> see above.
> >>
> >> > 3. How to handle queue overflow/clustering ? (Say queue is full then
> it
> >> > sends message to another exchange/queue combination ? I could not
> make
> >> out
> >> > from documentation)
> >> >
> >> > Thanks,
> >> > Jigar
> >> >
> >> > --
> >> > View this message in context:
> >>
> http://qpid.2158936.n2.nabble.com/JMS-Api-and-multiple-queue-per-exchange-tp7236719p7236719.html
> >> > Sent from the Apache Qpid users mailing list archive at Nabble.com.
> >> >
> >> > ---------------------------------------------------------------------
> >> > Apache Qpid - AMQP Messaging Implementation
> >> > Project:      http://qpid.apache.org
> >> > Use/Interact: mailto:[hidden email]<
> http://user/SendEmail.jtp?type=node&node=7240839&i=1>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> Apache Qpid - AMQP Messaging Implementation
> >> Project:      http://qpid.apache.org
> >> Use/Interact: mailto:[hidden email]<
> http://user/SendEmail.jtp?type=node&node=7240839&i=2>
> >>
> >>
> >>
> >> ------------------------------
> >>  If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
>
> >> .
> >> NAML<
> http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> >>
> >
> >
> > --
> > View this message in context:
> http://qpid.2158936.n2.nabble.com/JMS-Api-and-multiple-queue-per-exchange-tp7236719p7246944.html
>
> > Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[hidden 
> email]<http://user/SendEmail.jtp?type=node&node=7247428&i=2>
>
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://qpid.2158936.n2.nabble.com/JMS-Api-and-multiple-queue-per-exchange-tp7236719p7247428.html
>  To unsubscribe from JMS Api and multiple queue per exchange, click 
> here<http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7236719&code=YnVnbWFpbEBqaWdhcnNoYWgubmV0fDcyMzY3MTl8NTA1ODg2NDEz>
> .
> NAML<http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>


--
View this message in context: 
http://qpid.2158936.n2.nabble.com/JMS-Api-and-multiple-queue-per-exchange-tp7236719p7248283.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

Reply via email to