• 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
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

declarative security management Vs programmatic security management

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have some questions related with security management,
1. If i use declarative security management, is that meaning that I don't have to do any login related model anywhere.
2. In petstore, It does not use any of the three login mechanisms specified by the J2EE platform (HTTP basic authentication, SSL authentication, or form-based login). But why? is it only because they want to decouple USER module and Customer module?
3. In petstore, there is a stateful session bean,ShoppingControllerEJB, which is used to cache the current customer, shoppingcart, etc.. My question is, when are those stuff set in the ShoppingControllerEJB, is it set when login? if so, if petstore also uses declarative security management, how could those info(for ext., customer) be set in the ShoppingControllerEJB?
I know those questions may be stupid or confusing, but I am really feeling uncertain about those issues.
Thanks for your reply!
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic