TransportClient in a JEE container is
better for separation of concerns.
Jörg
On Tue, Sep 9, 2014 at 4:25 PM, Tasha CARL wrote:
>If you use NodeClient in JEE container with data, but being part of an ES
>cluster: yes and no.
(think you mean without data)
That's what
t; If you use TransportClient: no, you just connect a client to an existing
> ES cluster which runs outside JEE.
>
> Jörg
>
>
> On Tue, Sep 9, 2014 at 10:32 AM, Tasha CARL wrote:
>
>> Let me ask a different question then:
>>
>> Do you agree when I say that if you
and they will never do like this. You will challenge
> many fields: resource allocation, reduced performance, less throughput,
> less fault tolerance, distributed JVM orchestration etc.
>
> Jörg
>
>
>
> On Tue, Sep 9, 2014 at 9:57 AM, Tasha CARL wrote:
>
>> >Elas
>Elasticsearch was never designed to run as a container managed Java EE
>component in a Java EE container, so the question about thread creation
>is unrelated.
That's exactly my point and that's why I ask this question.
>If you want to use an ES client from within a Java EE container,
>sta
