Mailing-List: contact users-help@deltaspike.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@deltaspike.apache.org
Received-SPF: pass (athena.apache.org: domain of deven.phillips@gmail.com
 designates 209.85.213.182 as permitted sender)
MIME-Version: 1.0
Date: Mon, 12 Jan 2015 21:41:09 -0500
Message-ID: 
 <CAJw+4NDp2MAMGN+4zfLsLZWc7pdBuP78pqqc164WiEnfUpV6zg@mail.gmail.com>
Subject: Jetty WebSocketClient Causing Scope Issues . . . I think...
From: Deven Phillips <deven.phillips@gmail.com>
To: users@deltaspike.apache.org
Content-Type: multipart/alternative; boundary=e89a8ffbae6d2c3e80050c7f8e59

--e89a8ffbae6d2c3e80050c7f8e59
Content-Type: text/plain; charset=UTF-8

So, I am trying to use DeltaSpike in an application which also uses Jetty's
WebSocket API (for a client connection)... The problem I appear to be
having is that when Jetty fires up separate threads for the WebSocket
client/handlers, they are not being properly scoped for CDI... When I try
to do certain operations with injected resources, I get:

UpdateSocket:199 - WELD-001303 No active contexts for scope type
javax.enterprise.context.RequestScoped

I read a post on StackOverflow which suggests that for each new thread I
need to create a request scope.

http://stackoverflow.com/questions/26631093/no-active-contexts-for-scope-type-javax-enterprise-context-requestscoped-when-in

How do I do that in a way that is not WELD specific?

Thanks in advance!

Deven

--e89a8ffbae6d2c3e80050c7f8e59--