Hi Romain,
thanks, I already guessed something like this. But is there some pattern to
avoid this or work around or something I could use to make it work?
Basically it means I may not use any cdi on jpa entities whatsoever and that is
quite a constraint :)
kind regards
Reinis
The alternative is to just inject the EJB and call the method directly
here.
On Mon, Apr 15, 2013 at 8:14 AM, to...@orbit-x.de wrote:
Hi Romain,
thanks, I already guessed something like this. But is there some pattern
to avoid this or work around or something I could use to make it work?
-Ursprüngliche Nachricht-
Betreff: Re: Re[2]: JPA issue in combo with @SessionScoped
Von: John D. Ament john.d.am...@gmail.com
An: users@tomee.apache.org
Datum: 2013/04/15 15:18:50
The alternative is to just inject the EJB and call the method directly
here.
On Mon, Apr 15, 2013 at 8:14 AM, to...@orbit
-related in jpa.
I heard (from Struberg?) that DeltaSpike is goin to offer a solution for
this?
Br
Reinis
-Ursprüngliche Nachricht-
Betreff: Re: Re[2]: JPA issue in combo with @SessionScoped
Von: John D. Ament john.d.am...@gmail.com
An: users@tomee.apache.org
Datum: 2013/04/15 15
.
I heard (from Struberg?) that DeltaSpike is goin to offer a solution for
this?
Br
Reinis
-Ursprüngliche Nachricht-
Betreff: Re: Re[2]: JPA issue in combo with @SessionScoped
Von: John D. Ament john.d.am...@gmail.com
An: users@tomee.apache.org
Datum: 2013/04/15 15:18