If you are 'reloading' an InitialContext to add new JNDI config, then depending on how you do that exactly I'd guess your application is coupled to either the syntax of the properties it uses or maybe just the implementation class. In either case, you could as well use session.createQueue(<name>) etc to create the destination objects instead, its no more provider-specific behaviour than the former.
The context can actually also create Queue/Topic objects without predefined config using the prefixes "dynamicQueues/" or "dynamicTopics/" on the lookup, e.g looking up "dynamicQueues/myQueue" will give you a Queue destination object for "myQueue". Robbie On 14 March 2018 at 17:29, Cyril Micoud <cmic...@vitechnology.com> wrote: > We use Qpid Broker-J 7.0.x... > > We have build a REST service based on Retrofit but it is very coupling with > POJO structure (we use Custom POJO instead of Map<String, Object> return by > REST api due to the simplicity to understand which object we manipulate). > After see management via JMS message, I think to me it is pobably the best > way to manage Broker configuration... > > But, for the moment, I am not able to use a queue or topic if it is not > already present in JDNI properties (InitialContext). > After each REST creation, I must reload the InitialContext with the new > queue... > > Perhaps, vertx-proton was better in that case... > > Best regards > > Cyril > > -----Message d'origine----- > De : Rob Godfrey <rob.j.godf...@gmail.com> > Envoyé : mercredi 14 mars 2018 17:19 > À : users@qpid.apache.org > Objet : Re: Qpid JMS 0.30.0 or Qpid Proton-J 0.26.0 to point-to-point message > exchange? > > On 14 March 2018 at 17:13, Cyril Micoud <cmic...@vitechnology.com> wrote: > >> Thanks Gordon and Robbie for your answers. >> >> I have found the vertx-proton just few second before your response... >> it is very simple and I think we are going to use it to provide a >> light and simple server on our "client" java side. >> >> About JMS, I have seen a link (but where?) to manage VirtualHost, >> Exchange and Queue directly via message, it is always possible with >> Qpid JMS 0.30.0 or our only way is the REST api? >> >> > Which broker are you using? Unfortunately there is not yet a standardised > way to manage different brokers. > > -- Rob > > >> Thanks again a ot by advance, >> Best regards, >> >> Cyril >> >> >> -----Message d'origine----- >> De : Gordon Sim <g...@redhat.com> >> Envoyé : mercredi 14 mars 2018 14:20 >> À : users@qpid.apache.org >> Objet : Re: Qpid JMS 0.30.0 or Qpid Proton-J 0.26.0 to point-to-point >> message exchange? >> >> On 14/03/18 12:19, Cyril Micoud wrote: >> > how each system knew the dispatch router? >> >> They just need a host and port; that would be the same even if one was >> directly connecting to the other. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For >> additional commands, e-mail: users-h...@qpid.apache.org >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
