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?
Blake Minghelli<br />SCWCD<br /> <br />"I'd put a quote here but I'm a non-conformist"