Hi,
I have the following situation: JBoss 3 RC3, Oracle db. 3 tables:
table1 with prim key: pk1
table2 with prim key: pk2
table3 with primary key: pk1+pk2
All tables have their entity beans.
Also entity bean 3 has relations to entity 1 and 3 (n-1 relationships).
The problem is that when I crea
Hello Wouter,
AFAIK it's still not possible.
If entity 3 serves only to provide relationship between 1 and 2 you could
remove it at all and let JBossCMP handle the relationship.
Thursday, May 30, 2002, 11:49:37 AM, you wrote:
WK> Hi,
WK> I have the following situation: JBoss 3 RC3, Oracle db.
On Thu, 2002-05-30 at 10:06, Alex Loubyansky wrote:
> Hello Wouter,
>
> AFAIK it's still not possible.
If that's right, then this is a pretty fundamental flaw. There are
reasons other than managing an m:n relationship for having a field be
part of a primary key and a foreign key.
If it's true t
For the millionth time this is not a flaw, oversight, bug, etc. It is
the way I coded it. I knew what I was doing, and I knew some would fine
it unacceptable. This is not an easy feature to code, so I decided to
delay it until the spec required features were done. I will add it in a
future
Apololgies for any offence I have caused, Dain. I am impressed by the
general quality of your work and that of the other JBoss authors, but I
had inferred from the "RC3" designation that all key functionality would
be present and more-or-less functional.
Your answer implies that the ability to ha
Suffer, that is an interesting verb. The spec does not talk about
mappings at all (you should read it), any specific mapping is outside of
the specification. The spec does say that a CMR field can not be a
primary key field.
There is a person working on implementing this feature right now.
