Win a copy of Mastering Corda: Blockchain for Java Developers 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
  • 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

Q: EJB must not define class in package

 
Ranch Hand
Posts: 137
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What does it mean when the spec. says:

EJB must not define a class in a package?

Anyone has an example?
Thanks.
Yan
 
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


As a Bean Provider, your deliverable is an ejb-jar file with your beans/interfaces/deployment-descriptor. This ejb-jar file can possibly be mixed with other ejb-jar's from the application-assembler, to better fit a domain, based on the requirements. And I guess that's why EJB spec does not recommend putting classes in packages.

HTH,

-Fazal.
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would have thought that this is about disallowing the use of definePackage() and defineClass() of ClassLoader.
 
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I read some where that defining beans in packages, will be a security hole.
If it is the case, is there any body who knows why and how?
reply
    Bookmark Topic Watch Topic
  • New Topic