-
1. Re: PersistenceContext causing bean's jndi entry to disapear
jplessinger Mar 28, 2006 3:53 AM (in response to jplessinger)I renamed entityManager to em and new it woks fine. now out of curiosity is this how annotations are suppose to work?
-
2. Re: PersistenceContext causing bean's jndi entry to disapear
epbernard Mar 30, 2006 5:39 PM (in response to jplessinger)you mean you replaced
@PC EntityManager entityManager
to
@PC EntityManager em
and it now works?
If this is the case, there is something wrong in your code somewhere like overriden local variable -
3. Re: PersistenceContext causing bean's jndi entry to disapear
jplessinger Mar 31, 2006 1:58 AM (in response to jplessinger)Yes that's all I have done. em is not referenced or overridden anywhere in my code. only used (IE em.find() etc..)
-
4. Re: PersistenceContext causing bean's jndi entry to disapear
epbernard Mar 31, 2006 3:03 AM (in response to jplessinger)I don't see anything in our code base that could do such a behavior
-
5. Re: PersistenceContext causing bean's jndi entry to disapear
jplessinger Mar 31, 2006 4:01 AM (in response to jplessinger)Just thought I would fully verify my problem.
My bean class is empty except for empty method declarations. if the EntityManager is named anything else other then em the beans local interface is unavailable in the jndi tree. Calling the EntityManager em or removing the annotation makes the bean available in the jndi tree.
As far as the entityManager named varable actual working I can't tell due to disappearance from the jndi tree.