• 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
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

Why "ejb-link" in "ejb-local-ref" is optional ?

 
Ranch Hand
Posts: 117
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From the HFB mock exams, P.663 Q15 and the spec (p.466), why <ejb-link> is optional in <ejb-local-ref> ?

How to define "optional" ?

What happen during runtime if I have a <ejb-local-ref> elements but don't write the <ejb-link> ?
 
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm not really sure why they're optional. I think it has to do with the different "roles" involved in developing, packaging, and deploying an application. For the ejb-link, etc ... the spec officially says that by the time the app is deployed they need to be filled in. But, it's technically the job of the deployer "role"/person, so the developer doesn't really have much to do with it.

Then it gets messy with ejb-links to EJBs in other EARs, etc. Fun stuff. So I would imagine that it's optional so the file will validate, although the nodes should be there by the time it hits the container. I think.
reply
    Bookmark Topic Watch Topic
  • New Topic