Wildfly Alpha3, Dynamic queue creation and jndi lookup

[fuinhaazul]

Hi there.

Currently, I have a JMS project that the remote clients creates its on queues and then connects to it.

Today i´m using the core API to do this:

First i use JMX:

private JMSServerControl jmsServerControl
...

and after this, i connect to the queue:

...
HornetQConnectionFactory fac = new HornetQConnectionFactory(
                                        false,
                                        transportConfiguration);
...

But now, i´m trying to switch to pure JMS doing JNDI lookup.  After a small fight with the remote URL I connected with the server with:

private static final String PROVIDER_URL = "http-remoting://localhost:8080";

But now i need to discover how to create the JNDI destinations dynamically. The queue "queue.Teste" exists, but the JNDI name doesnt.

Exception in thread "main" javax.naming.NameNotFoundException: queue/Teste -- service jboss.naming.context.java.jboss.exported.queue.Teste

Any hints to achieve this?

PS: What i´m trying to do is exactly what this JIRA is saying, https://issues.jboss.org/browse/HORNETQ-302

Thanks !!!

[jmesnil]

If you are using WildFly, the best way to create dynamically the queues is to use its management API either through HTTP[1] or with its native Java version[2]

[1] https://docs.jboss.org/author/display/WFLY8/The+HTTP+management+API

[2] https://docs.jboss.org/author/display/WFLY8/The+native+management+API

[fuinhaazul]

Thanks. I will look these links.

Its the second time i need to work with jms and again the requirement is create queues dynamically :-) 

Maybe in the future this can be an hornetq feature?

Thanks again

[jmesnil]

Please note that there are already some way to create queues dynamically. The issue is how much dynamic you want them to be

For simple request/reply use cases, JMS allows to create temporary queues. You can not bind them to JNDI but they can be passed to messages using the JMSReplyTo header.

With JMS 2.0, it is also possible to have queues (and topics) defined with the deployed archives. All the components of this archive can then use them through JNDI and they are available for the lifetime of the deployed archive.