Re: [weld-dev] Maintenance release
How will this play together with the new @Optional you proposed for the MR?
As far as I've seen in the EJB-3.0 spec and from javax.persistence, the container is
not explicitly obligated to throw an Exception if the right EntityManagerFactory or an
EntityManager cannot be found.
OWB currently injects null and logs an INFO if a @PersistenceContext or @PersistenceUnit
cannot be found.
LieGrue,
strub
--- On Thu, 12/31/09, Gavin King <gavin.king(a)gmail.com> wrote:
From: Gavin King <gavin.king(a)gmail.com>
Subject: Re: [weld-dev] Maintenance release
To: "Java Community Process JSR #299 Expert List" <JSR-299-EG(a)jcp.org>,
"Weld-Dev" <weld-dev(a)lists.jboss.org>
Date: Thursday, December 31, 2009, 12:02 PM
On Thu, Dec 31, 2009 at 4:58 AM,
Gavin King <gavin.king(a)gmail.com>
wrote:
> We should say that if this annotation is used on a
class annotated
> @Alternative, then it is only activated if the
alternative is enabled.
Hrm. This also opens up a question about
@Resource/@PersistenceContext/etc. Is it expected that the
container
validates these dependencies and fails deployment if they
don't exist?
I think it is, right? At least, I think some containers
behave this
way. Then we should say that this validation should *not*
happen if
the annotation appears in a class annotated @Alternative. I
have no
idea what the right language would be...
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev