• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

EJB 3.0: annotations vs deployment descriptors

 
Ranch Hand
Posts: 331
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I just read a JavaWorld article about EJB 3.0. The pieces of the spec regarding eliminating home interfaces, making entity beans POJOs, etc sound great, like they will really help make developing EJB apps easier.

However, I'm not sold on annotations. EJB 3.0 seems to be all about annotations. That seems like you are doing the same thing as deployment descriptors except that now you have hard-coded them into your classes. And, for entity beans, annotating the table/column names in the class files seems like it would be severly impacting portability.

The EJB 3.0 expert group consists of experts (duh), so I'm not doubting their design. I have very little EJB experience to draw on. But maybe someone can help clarify how annotations are a better way to go?
 
"To do good, you actually have to do something." -- Yvon Chouinard
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic