• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Access to Resource Managers & other EJB's

 
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Kathy,

in page 80 spec, the methods of the stateful session bean with CMT are given which can access the methods on SessionContext and the resoures.

there is

ejbCreate
ejbRemove
ejbActivate
ejbPassivate

can access

Resource manager access
Enterprise bean access

even if they are in unspacified transaction context the reason may be this
given at page 81 spec

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.

In above case we have Security context because it is Stateful session bean.

But now my qestion is that if this is allowed because of security context then even In CMT

afterCompletion<

execute in unspacified transaction and have the security context to it then
why

Resource manager access
Enterprise bean access

is not allowed in this case. Pls answer this i have very big doubt.

Thanks!!
Sandy
[ December 07, 2004: Message edited by: sandeep vaid ]
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic