>
> Jörg and Lukáš,
>
Thank you both for your suggestions, they are very helpful. Looks like I
have more research to do!
Thanks Again!
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving em
Craig, the war-es plugin uses a similar servlet-based approach. It is a
disguised client node, not a TransportClient. The plugin is not ready for
deployment as a WAR. You have to fix some of the code by yourself, maybe
this helps:
https://github.com/elasticsearch/elasticsearch-transport-wares/pull/
Craig,
if you want you can also check how we do it for EAP6,
https://github.com/searchisko/searchisko (we use CDI)
What we do is similar to what David already mentioned, we use embedded Node
for development (works also on OpenShift) and TransportClient for
production where Elasticsearch cluster ca
Hi Jörg,
>
> Thanks for the suggestion. I don't think I will be able to speak at the
> same level of understanding that you have in regards to this issue. Are you
> suggesting using an approach such
> as https://github.com/elasticsearch/elasticsearch-transport-wares to
> include ES in the same
Craig, for a POC, you can deploy a WAR into Wildfly (JBoss) with a
TransportClient as a singleton, for example in a ServletContextListener, it
works perfectly for me.
You should not depend Wildfly instances on ES nodes. If frontend is not
dependent on backend, you can scale out both independently,
Hi Lukáš,
Thanks for your reply. I don't think there is really any advantage. The
company I work for likes to run everything on JBoss, therefore in order to
make them happy we always have to explore JBoss as an option. The web
application I am working on as a POC will run on JBoss and I am ho
Craig,
out of curiosity, what is the advantage of such deployment? Why you want to
run JBoss server (or EAP) for each Elasticsearch node?
Regards,
Lukáš
On Tue, Mar 11, 2014 at 1:01 PM, Craig Graham wrote:
> Hi David,
>
> Thanks for the quick response. For the purposes of this POC we need to
Hi David,
Thanks for the quick response. For the purposes of this POC we need to
mock an environment where ElasticSearch is running similar to how it does
"out of the box" in Jetty, except use JBoss instead. We would like to have
an instance of JBoss which we can deploy ElasticSearch to and i
I did some years ago.
I found that using a Transport Client was easier for me.
If it's for a POC, I would probably go for a an embedded Node in the web
application.
This is what we did in http://www.scrutmydocs.org/ project but I did not test
it on JBoss, only tomcat.
Easy to start: just deploy
I have just started working with ElasticSearch while creating a POC search
application at work. I was wondering if anyone had experimented with
running ElasticSearch in JBoss and could provide some direction as to how
to accomplish this?
Thanks!
--
You received this message because you are s
10 matches
Mail list logo
