• 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

operations allowed in the methods of SFSB

 
Ranch Hand
Posts: 252
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Reference: EJB 2.0 Final Release
Page: 80/81
ejbRemove() and afterComplete() methods do not operate under a transaction context.
on Page 81: Invoking the getCallerPrincipal and isCallerInRole methods is disallowed in session bean methods for which the container does not have a client security context
both ejbRemove() and afterComplete() methods can access getCallerPrincipal and isCallerInRole which means that both are in Client Security COntext (is it not?). If afterComplete() is in CLient Security Context it should be able to access resource managers and enterprise beans but the spec says that (on page 80) afterComplete() can't access resource managers and enterprise beans.
This is ambiguous to me, could someone explain this?
Thanks,
Santosh R
 
Ranch Hand
Posts: 1392
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This was discussed HERE before. But no conclusion was made.
Joyce
[ April 12, 2004: Message edited by: Joyce Lee ]
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic