Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript 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 ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown


Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i came thro the following statemnt abt ejb,
can anyone explain it..

"The enterprise bean implementation is not supposed to implement the bean's RemoteInterface directly, so that clients cannot by mistake bypass the container-generated EjbObject that wraps the BeanImplementation and does implement the RemoteInterface. Yet we would like to have some compile time confirmation that our implementation implements all of the business methods advertised in the RemoteInterface."

Posts: 304
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yeah, that was one of the things that just didn't sit right about previous versions of EJB and that was fixed in EJB 3.0. In EJB 2.x you have to wait until the EJB compiler does the verification either at deployment or at EJB-compile time (if your server supports doing it in advance of deployment).

Switching from electric heat to a rocket mass heater reduces your carbon footprint as much as parking 7 cars. Tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic