Originally posted by norman richards:
It's hard to say how JSR 175 metadata will be applied to EJB development. I wouldn't shed any tears if XDoclet needed to generate a few less things. I'd love it if XDoclet could focus more on the complex generation tasks like value objects and DAOs and less on generating yet-another-redundant interface. In addition to seeing how metadata can replace code generation, I'm curious to see how metadata can be used as an input source for XDoclet code generation.
Does XDoclet have support for VAO and DAO generation? I've used XDoclet months ago but never used that. It'd be awesome!
There's also a <dao> subtask that can generate DAO interfaces for your BMP entity beans. It just generates an interface, no SQL or anything like that. And it's only useful with BMP entity beans. I've only used this subtask with a quick example in the book and have since forgotten it...I'm not a BMP entity bean fanatic and would prefer CMP entity beans (actually, I prefer Hibernate over any entity bean, but that's another story.)
Another nice feature is that you can generate multiple views. You might want one value object that just has your primary key and a couple of attributes to use on a list/summary page and then have another value object that contains the full view (maybe aggregating data from related beans) that you want to use when you display the details of a specific item.
It's very handy...