Hi Stephen, great. java would be best, like an additional command extension to the activemq-admin tool. this is the easiest to test and validate across platforms.
I was thinking something like a 'jndi-bind' command, that would take an optional contextName parameter and an activemq-jnid.properties and 'bind' the contents of the activemq context into whatever new InitialContext().lookup(< contextName>) returns. In this way, what ever system wide jndi environment is enabled, be it FScontext or a third party jndi server, it can get auto propagated with activemq entities. One problem is the definition of an activemq connection factory, with relevant configuration. Using an existing activemq.jndi properties file may the simplest way (or at least a well known way) to define connection factories. But this may not be what you are thinking, feel free to do what every you think is best and whatever suits your use case best! we look forward to your contribution, thanks, Gary. On 11 May 2010 12:13, Scawa1952 <mcconnell_step...@yahoo.com> wrote: > > Thank you for your prompt reply. > > I noticed that most of the information to create the .bindings file is > available when one performs an activemq-admin query command. One just has > to parse through, pick up the information and generate it. > > Sounds like an easy fun project. I'll see what I can do. Do you want this > as a bash, perl script or in java? > > Stephen McConnell > > > Gary Tully wrote: > > > > There is no such tool for activemq at the moment but we do love > > contributions. > > > > In activemq, destinations are created on demand and the activemq client > > side > > memory jndi provider <http://activemq.apache.org/jndi-support.html> will > > respond with dynamically created destinations for the /dynamic* context > so > > very often the need for static configuration can be avoided. > > > > For consistency though, it is nice to be able to access all JMS resources > > from jndi so this would be a nice enhancement. > > Statically configured destinations could be auto registered in jndi and a > > 'bind' extension to the command line > > tool< > http://svn.apache.org/viewvc/activemq/trunk/activemq-console/src/main/java/org/apache/activemq/console/command/ShellCommand.java?view=markup > >could > > deal with registering factories. > > > > On 10 May 2010 18:48, Scawa1952 <mcconnell_step...@yahoo.com> wrote: > > > >> > >> We are using several JMS servers at our organization. I have found > >> documentation on how to generate a .bindings file for those JMS servers, > >> but > >> have not found anything on how to do so for the ActiveMQ .bindings file. > >> There is an example of one on this site, but usually these files can be > >> generated by the server at startup or there is a command that will do > >> so... > >> > >> Where is the documentation for ActiveMQ.. > >> > >> Thanks > >> -- > >> View this message in context: > >> > http://old.nabble.com/Generating-.bindings-file-for-RefFSContextFactory-tp28512685p28512685.html > >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >> > >> > > > > > > -- > > http://blog.garytully.com > > > > Open Source Integration > > http://fusesource.com > > > > > > -- > View this message in context: > http://old.nabble.com/Generating-.bindings-file-for-RefFSContextFactory-tp28512685p28522772.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
