.
>
> LieGrue,
> strub
>
> --- Gurkan Erdogdu schrieb am Di, 16.2.2010:
>
> > Von: Gurkan Erdogdu
> > Betreff: Re: Reservation EntityManagerUtil
> > An: dev@openwebbeans.apache.org
> > Datum: Dienstag, 16. Februar, 2010 14:48 Uhr
> > >Writing some
n Erdogdu schrieb am Di, 16.2.2010:
> Von: Gurkan Erdogdu
> Betreff: Re: Reservation EntityManagerUtil
> An: dev@openwebbeans.apache.org
> Datum: Dienstag, 16. Februar, 2010 14:48 Uhr
> >Writing something like
> > private @Produces @PersistenceContext(unitName=
Oki, that makes perfect sense!
The passivation capability mentioned in 7.3.6 also explains why we need a
ResourceBean!
txs and LieGrue,
strub
--- Gurkan Erdogdu schrieb am Di, 16.2.2010:
> Von: Gurkan Erdogdu
> Betreff: Re: Reservation EntityManagerUtil
> An: dev@openwebbeans.a
>Writing something like
> private @Produces @PersistenceContext(unitName="
reservation") EntityManager entityManager;
>
> @Produces @RequestScoped
@org.apache.webbeans.reservation.bindings.EntityManagerQualifier
> public EntityManager createEntityManager()
> {
> return entityManager;
> }
This
Mark,
I skim over JSR-299 specification, and it supports two style of injection .
As it states in 3.5 via ResourceBean and direct injection of resources that
are defined within Java EE specification.
Section 7.3.6 explains lifecycle of the resources. And it states that if you
inject resources wit
Hi Gurkan!
It seems we have a different understanding on 3.5.1 and I beg you to stop
changing this parts until Gavin or Pete answers our question. We must get a
clear understanding on these points before releasing M4 at least!
Imho 3.5.1 is only meant as an example and directly injecting
@Pers
