Hi Prikshit, Is is possible to launch the Qpid broker within the same JVM and we can point out how to do this if you decide to go down that route, but I'm still a little unclear on your actual intentions and whether this would really be a good fit. Would you be looking to use the Qpid broker in actual deployment of the application, or only for use in the same JVM during testing whilst continuing to use the RabbitMQ broker for the final deployment?
If the latter, we normally wouldn't recommend such an approach as your testing then wouldn't be representative of your actual system. Whilst it can obviously be nicer to have components in the same JVM at times, is this really a hard requirement for you, i.e. is there a particular reason that having your tests launch the RabbitMQ broker as a standalone process isn't workable for you? What has your testing to date been doing in this area? Robbie On 5 August 2013 15:24, prikshit <[email protected]> wrote: > Hi Robbie, > > I need to have a broker which is running with in same JVM... and using > existing RabbitMQ clients. > > Thx, > Prikshit > From: Robbie Gemmell [via Apache Qpid developers] [mailto: > [email protected]] > Sent: Monday, August 05, 2013 7:23 PM > To: Chauhan, Prikshit > Subject: Re: STARTING/STOPPING Apache Qpid from Maven > > Hi Prikshit, > > Could you elaborate a little on exactly what you actually mean, as it isn't > entirely clear? > > E.g are you looking to use maven to start/stop the broker for use by some > external testing taking place, or are you looking for an embedded broker to > use during tests running within the same JVM? Would you be looking to use > the Qpid broker with pre-existing integration tests for an application that > would be using RabbitMQ clients, or are you looking to swap wholesale to > use Qpid clients as well? > > What is preventing you starting/stopping RabbitMQ using Maven? Obviously it > isn't written in Java, but that wouldnt seem to preclude it from being > started as an external process. > > Regards, > > Robbie > > Hi, > > For my integration testing, i am planning to migrate from rabbitMQ to > ApacheQpid, coz of > --> Maven do't support starting/ stopping RabbitMQ server > > Please suggest me should i use Apache Qpid to remove this dependency. > > Or do i have any other option. > > Thx, > Prikshit > > > > -- > View this message in context: > > http://apache-qpid-developers.2158895.n2.nabble.com/STARTING-STOPPING-Apache-Qpid-from-Maven-tp7588664.html > Sent from the Apache Qpid developers mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden > email]</user/SendEmail.jtp?type=node&node=7588701&i=0> > For additional commands, e-mail: [hidden > email]</user/SendEmail.jtp?type=node&node=7588701&i=1> > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > > http://apache-qpid-developers.2158895.n2.nabble.com/STARTING-STOPPING-Apache-Qpid-from-Maven-tp7588664p7588701.html > To unsubscribe from STARTING/STOPPING Apache Qpid from Maven, click here< > http://apache-qpid-developers.2158895.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7588664&code=cHJpa3NoaXRfY2hhdWhhbkBkZWxsLmNvbXw3NTg4NjY0fDIxMDc5MTkxNDU= > >. > NAML< > http://apache-qpid-developers.2158895.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://apache-qpid-developers.2158895.n2.nabble.com/STARTING-STOPPING-Apache-Qpid-from-Maven-tp7588664p7588703.html > Sent from the Apache Qpid developers mailing list archive at Nabble.com. >
