• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

quite pulzzed

 
chao cai
Ranch Hand
Posts: 154
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
� The ejbCreate<METHOD>, ejbRemove, ejbPassivate, and ejbActivate methods
of a session bean with container-managed transaction demarcation execute with an unspecified
transaction context. Refer to Subsection 17.6.5 for how the Container executes methods
with an unspecified transaction context.
� Accessing resource managers and enterprise beans is disallowed in the session bean methods
for which the Container does not have a meaningful transaction context or client security context.
[ejb2-spec pp81]

why in the method ejbPassivate or ejbActivate can access JNDI java:comp/env,Resource manager ,other Enterprise bean also it is denied in the same method of entity bean
 
Jesus Angeles
Ranch Hand
Posts: 2068
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
just my advice, you may tweak your thinking a little, by recognizing, that even though they are all ejbs, session, entity and mdbs have a lot of difference too, esp. the entity bean
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic