I don't know where this should fail, but it needs to fail somewhere, and if CDI isn't it, I trust there are people on this list the other EGs will listen to because too many of them ignore the users list, because you know, they're the "experts". public class EmProducer() { @PersistenceContext(type = PersistenceContextType.EXTENDED) EntityManager em; @Produces @RequestScoped public EntityManager getEntityManager() { return em; } } That should be a deployment exception stating it isn't valid (the @PersistenceContext injection). -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev

Yup this caused a lot confusion because some containers silently inject an Unmanaged EntityManager if it's not an EJB, others inject a Managed EntityManager _despite_ it's not an EJB, ... I'd say we should either define that it should inject an unmanaged EM or define to throw an Exception in that case. LieGrue, strub > ________________________________ > From: Dan Allen <dan.j.allen(a)gmail.com&gt; > To: Jason Porter <lightguard.jp(a)gmail.com&gt; > Cc: cdi-dev(a)lists.jboss.org > Sent: Wednesday, April 18, 2012 12:49 AM > Subject: Re: [cdi-dev] Needed failing for JPA / EJB > > > Note that the point here is the use of the extended persistence context injection on a regular managed bean, not an EJB. > > > -Dan > > > p.s. This lends itself well to an Arquillian test for demonstrating the current and desired exceptions. > > > On Tue, Apr 17, 2012 at 18:37, Jason Porter <lightguard.jp(a)gmail.com&gt; wrote: > > I don't know where this should fail, but it needs to fail somewhere, and if CDI isn't it, I trust there are people on this list the other EGs will listen to because too many of them ignore the users list, because you know, they're the "experts". >> >> >> public class EmProducer() { >> @PersistenceContext(type = PersistenceContextType.EXTENDED) >> EntityManager em; >> >> >> @Produces @RequestScoped >> public EntityManager getEntityManager() { >> return em; >> } >> } >> >> >> That should be a deployment exception stating it isn't valid (the @PersistenceContext injection). >> -- >> Jason Porter >> http://lightguard-jp.blogspot.com >> http://twitter.com/lightguardjp >> >> Software Engineer >> Open Source Advocate >> Author of Seam Catch - Next Generation Java Exception Handling >> >> PGP key id: 926CCFF5 >> PGP key available at: keyserver.net, pgp.mit.edu >> >> _______________________________________________ >> cdi-dev mailing list >> cdi-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/cdi-dev >> >> > > > > -- > > Dan AllenPrincipal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > > http://google.com/profiles/dan.j.allen > http://mojavelinux.com > http://mojavelinux.com/seaminaction > > > _______________________________________________ > cdi-dev mailing list > cdi-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/cdi-dev > > > _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev

I don't know where this should fail, but it needs to fail somewhere, and if CDI isn't it, I trust there are people on this list the other EGs will listen to because too many of them ignore the users list, because you know, they're the "experts". public class EmProducer() { @PersistenceContext(type = PersistenceContextType.EXTENDED) EntityManager em; @Produces @RequestScoped public EntityManager getEntityManager() { return em; } } That should be a deployment exception stating it isn't valid (the @PersistenceContext injection). -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev

I'm guessing the problem lies in the fact that the bean doing the producing is not itself scoped? On Wed 18 Apr 2012 11:25:06 AM EDT, Adam Bien wrote: > The code above should work for Java EE 7 and CDI 1.1. > The @RequestScoped @Produces below is not that reasonable, but @SessionScoped should work in CDI 1.1. > > On 18.04.2012, at 00:37, Jason Porter wrote: > >> I don't know where this should fail, but it needs to fail somewhere, and if CDI isn't it, I trust there are people on this list the other EGs will listen to because too many of them ignore the users list, because you know, they're the "experts". >> >> public class EmProducer() { >> @PersistenceContext(type = PersistenceContextType.EXTENDED) >> EntityManager em; >> >> @Produces @RequestScoped >> public EntityManager getEntityManager() { >> return em; >> } >> } >> >> That should be a deployment exception stating it isn't valid (the @PersistenceContext injection). >> >> -- >> Jason Porter >> http://lightguard-jp.blogspot.com >> http://twitter.com/lightguardjp >> >> Software Engineer >> Open Source Advocate >> Author of Seam Catch - Next Generation Java Exception Handling >> >> PGP key id: 926CCFF5 >> PGP key available at: keyserver.net, pgp.mit.edu >> _______________________________________________ >> cdi-dev mailing list >> cdi-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/cdi-dev > > > _______________________________________________ > cdi-dev mailing list > cdi-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/cdi-dev -- --- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev

The code above should work for Java EE 7 and CDI 1.1. The @RequestScoped @Produces below is not that reasonable, but @SessionScoped should work in CDI 1.1. On 18.04.2012, at 00:37, Jason Porter wrote: > I don't know where this should fail, but it needs to fail somewhere, and if CDI isn't it, I trust there are people on this list the other EGs will listen to because too many of them ignore the users list, because you know, they're the "experts". > > public class EmProducer() { > @PersistenceContext(type = PersistenceContextType.EXTENDED) > EntityManager em; > > @Produces @RequestScoped > public EntityManager getEntityManager() { > return em; > } > } > > That should be a deployment exception stating it isn't valid (the @PersistenceContext injection). > > -- > Jason Porter > http://lightguard-jp.blogspot.com > http://twitter.com/lightguardjp > > Software Engineer > Open Source Advocate > Author of Seam Catch - Next Generation Java Exception Handling > > PGP key id: 926CCFF5 > PGP key available at: keyserver.net, pgp.mit.edu > _______________________________________________ > cdi-dev mailing list > cdi-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/cdi-dev