> The biggest deficiency (IMHO) in EJB specification is that it doesn't > define component inheritance. The EJB component consists of remote
And lots of other things! > The <ejb-name> of the second part of the relationship is: > test.CatalogItem. However, there's no bean deployed by that name since > test.CatalogItem is abstract. If the <ejb-name> would be Product, then > "the poor man's component inheritance" would work. Any comments? It's a bug. Please file it in bugs db. Btw, there's a lot to improve in "relationship inheritance" so you define a relation say in a base class and relate it to another abstract bean and xdoclet again does the poor man's job to do a form of inheriting the relation for you. AFAIK the other end of a relation in ejb2 spec is always a bean with a specific type, you can't define an n-ary relation of different ejb types (and imho this is a big big limitation, or may I say CMP2 is totally unusable?). Ara. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
