• 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

Whose responsibility for the configuration sign-on info for resoruce manager?

 
Ranch Hand
Posts: 147
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Whose responsibility for the configuration sign-on info for resoruce manager? Yes, deployer if the <res-auth> is container, But if <res-auth> is application, that will be the bean provider's responsibility to configure the sign-on info programmatically. So both deployer and bean provider have the responsibility for the configuration sing-on info for resoruce manager. Any comments?
[ May 06, 2004: Message edited by: Alibabra Sanjie ]
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The Bean Provider uses the res-auth deployment descriptor element to indicate which of the two resource manager authentication approaches is used.
If the value of the res-auth element is Container, the Deployer is responsible for configuring the sign-on information for the resource manager.
 
Alibabra Sanjie
Ranch Hand
Posts: 147
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

...But if <res-auth> is application, that will be the bean provider's responsibility to configure the sign-on info programmatically...


In this case, the bean provider still have to specify the sign-on info programmatically in the bean class using the resource manager API. Deployer CANNOT define the sign-on info if the <res-auth> is Application!
 
Alibabra Sanjie
Ranch Hand
Posts: 147
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Anyone has any other idea?
reply
    Bookmark Topic Watch Topic
  • New Topic