[tonibeckman]

Hi Dain,

this seems like a big limitation, since it is very common to have a foreign key which is made up parly of a primary key of another table. Actually this happens so frequently, that I find the Entity concept difficult to apply to real life applications.

When I first looked at EJB 1.1 one and a half years ago I realized right away that concept behind the Entity Bean is great but that the implementation of it was poorly done and not very usefull.

Now I hoped with EJB 2.0 this would change. I'm trying to convince our company to use JBoss instead of BEA Weblogic, which is their prefered choice.

Now my question is, wether or not this feature will be supported in a future release of JBoss? Also I would like to know if this would have to be considered as a propiteray vendor extension - or if this is actually part of the offical EJB specification from sun microsystems and has not been implemented by the JBoss group yet (for whatever reasons - probably to busy)?

best regards,
Toni

[dsundstrom]

> this seems like a big limitation, since it is very
> common to have a foreign key which is made up parly
> of a primary key of another table. Actually this
> happens so frequently, that I find the Entity concept
> difficult to apply to real life applications.

Yes I am aware of the limitations. You can search the forums for my posts on this in the past and for the story as to why it is not currently implemented.

> When I first looked at EJB 1.1 one and a half years
> ago I realized right away that concept behind the
> Entity Bean is great but that the implementation of
> it was poorly done and not very usefull.

Yes the CMP 1.1 spec was mostly useless.

> Now I hoped with EJB 2.0 this would change. I'm
> trying to convince our company to use JBoss instead
> of BEA Weblogic, which is their prefered choice.

Life is better with CMP 2.0. If the current implementation does not make you happy and Weblogic satifies your needs, then go with Weblogic. It is a fair choice.

> Now my question is, wether or not this feature will
> be supported in a future release of JBoss?

Yes

> Also I would like to know if this would have to be
> considered as a propiteray vendor extension - or if
> this is actually part of the offical EJB
> specification from sun microsystems and has not been
> implemented by the JBoss group yet (for whatever
> reasons - probably to busy)?

The EJB specification does not talk about persistence mappings, so any mapping can be considered a "propiteray vendor extension." All the spec says is the data must be persisted.