Win a copy of AWS Security this week in the Cloud/Virtualization forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

mock exam doubt

 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi ,
I came across the following question in one of the mock exams.

<ejb-link> is provided by whom ?
a.Bean provider
b.Application Assembler
c.Deployer .

I think the valid options are a and b but the the correct answer is a,b,c . Why should deployer specify ejb-link .

Thanks
Arun
 
Author & Gold Digger
Posts: 7617
6
IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Strictly speaking, only answer b should be correct. In the EJB 2.0 specification, the Bean Provider is just someone who provides EJBs, and thus, does not need to link beans together. However, the Application Assembler is a person who binds beans together in order to build up a concrete application. Agreed, sometimes the Bean Provider and the Application Assembler are one and the same person, and thus, the roles are somehow mixed. The only mention about the Deployer having something to do with the ejb-link element is made in section 20.3.3 of the spec where it is stated that the Deployer should bind the EJB reference to the home of the EJB specified as the link's target.

To sum up, the Bean Provider only provide isolated beans and does not wire beans together. Thus, no need to mess with ejb-link.
The Application Assembler is the one who ties all beans together, and thus, he needs to provide the ejb-link element.
The Deployer's role is limited to binding references to the respective EJB homes for each ejb-link element.
 
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
I think i have another question related to this..?

If Bean Developers responsibility is to provide EJB's whos responsible to write <relation> tags for entity beans
is it deployer, App Assempler or bean proider
 
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

In the spec it mentions that the bean provider must define the relationships of the beans �The entity Bean Provider must specify in the deployment descriptor those persistent fields and relationships for which the Container must handle data access.� P127

Hope this helps.
 
You’ll find me in my office. I’ll probably be drinking. And reading this tiny ad.
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic