On 17 Jun 2014, at 15:46, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
Jeff,
this is not about mgmt api exposure if I understood question correctly.
It is question on level of msc services.
Code inside services cannot access JNDI at all, so injecting service as dependency is
only solution.
I may not have been clear enough.
I advised to depend on the JNDI binding as a service using the
ContextNames.bindInfoFor(name).getServiceName().
As far as I can tell, this is the only way to depend on the ConnectionFactory from inside
the msc services.
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/