Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring 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
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

EJB Programming restrictions

 
Ranch Hand
Posts: 418
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I read follwoing in Mikalai 's notes -
The enterprise bean must not attempt to define a class in a package
Ehat does this means?
 
Author & Gold Digger
Posts: 7617
6
IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As stated in section 24.1.2 of the EJB 2.0 spec (p. 496), allowing an enterprise bean to define a class in a package would create a security hole. Note that the word "define" must be taken in the sense of the Classloader.define() method, in which a byte array representing a class can be passed in argument and this action would result in the loading of a class into the JVM. Imagine what could happen if a bean could do that. Since there is no way to trust 100% Bean Providers, the spec makes sure that such things as custom class loading should (must) not happen in order to ensure the integrity of the application server.
 
Rashmi Tambe
Ranch Hand
Posts: 418
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thnaks Val !
 
    Bookmark Topic Watch Topic
  • New Topic