My experience with JMS is very limited, so my reply may be fully wrong.
ElasticSearch has a RabbitMQ (AMQP) river plugin. JMS is pretty
similar to AMQP. So, you can write a new river plugin for JMS by using
the RabbitMQ river plugin as a reference. I believe it may not be too
tough to do, specially if you are an expert in JMS.
A slightly less attractive alternative would be to use an AMQP/JMS
bridge in between - http://github.com/imatix/openamq-jms (this works
with RabbitMQ, but with AMQP spec 0.8.x and not 0.9-1)
On Thu, Oct 14, 2010 at 9:42 PM, Stephen firstname.lastname@example.org wrote:
My company is interested in implementing ElasticSearch for a fairly
large dataset, and things would be much easier if we could publish
messages to an ActiveMQ (since we're using Enterprise Java) that ES
would listen on.
Do folks have an idea of how hard it would be to implement this
plugin? We may be willing to provide some development time, but a
rough idea of complexity would help our planning process.
Thanks a bunch!