You might be looking for something a lot more complicated than
necessary for ActiveMQ. What exactly do you want to look up that
can't be configured in jndi.properties?
thanks
david jencks
On Dec 24, 2008, at 7:15 AM, KLA2008 wrote:
Hello Joe,
jndi.properties file is used by client application. This file set
the JNDI
properties among wich "java.naming.provider.url" whose value refer -
in case
of FileSystem based JNDI- to the directory path containig the
bindingfile.
(example : java.naming.provider.url=file://D:/Dev/jndicontext).
Generally, the Broker (MOM) administration tools allow automatic
generation
of the .binding file based on created ConnectionFactories and Queues.
So for a full JNDI support , we need both : .binding and
jndi.properties.
Regards,
KLA
KLA2008 wrote:
Hi all,
I'm giving a Try to ActiveMQ 5.2, and I'm using JNDI (FileSystem
stored)
to access my adminstrated objects.
I've been looking around for how to generate the ".binding" file
and all
that I've found is this tutorial with a sample for ActiveMQ 4.X,
and it
did not work for me ( http://activemq.apache.org/sun-jndi.html )
How can we generate the .binding file automatically from ActiveMQ ?
(like
we do with WebSphereMQ or SUN openMQ) please ?
If there is no such tool, is there a .binding sample for ActiveMQ 5.2
please ?
Regards,
KLA
--
View this message in context:
http://www.nabble.com/FileSystem-JNDI-Context-for-ActiveMQ-5.2-tp21156854p21156879.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
