Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EJB Programming restrictions

 
Rashmi Tambe
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?
 
Valentin Crettaz
Gold Digger
Sheriff
Posts: 7610
  • 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 !
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic