[Martin_Kersten]

Hi there,

I’ve created a CMP entity bean and also set some @ejb.persistence sql-type=”type” xdoclet tags. Everthing is created well within jbosscmp-jdbc.xml. But the sql-type informations are missing.

What am I doing wrong?

Thanks

[Scott Anderson]

Martin,

I wanted to reply so you didn’t think you were being ignored, but the short answer is that I don’t know. We really don’t use Entity Beans at all in any of our consulting work so I don’t have any experience with the SQL generation capabilities or inabilities of XDoclet.

To run this down, you can either look at the XDoclet reference manual bundled in the MyEclipse User Guide or go directly to the XDoclet site (http://xdoclet.sourceforge.net). There may be something in their forums or bug database also.

Sorry I can’t be of more help. Any users out there doing this?

–Scott
MyEclipse Support

[Martin_Kersten]

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?

[Author]

Posts