No problem scott. I am using a little workaround right now. I just disallow to create a table for CMP entity beans. Therefore the tables representing entity beans informations has to be created before the bean can be deployed. It’s even a better way I think. It’s more flexible. The pain is, that it requires additional informations and documentation.
@scott wrote:
We really don’t use Entity Beans at all in any of our consulting work
If I am allowed to aks – why is that so? Is there anything wrong with entity beans – meaning something I should know ;). I am using the entities to port a midsize database application (administration part) to J2EE. As far as I get along with the task, it seams to work well.
But there seams to be a trend to use BMP + DAO instead of CMP for entity beans. At least for entity beans aggregating informations of more then one table, I can understand why. But is there a major gap about CMP, I don’t know yet?