Hi Gianny,
Here is the code
snippet for supporting the first scenario.But this will not support the
second scenario we discussed.
Thanks
Manu On 1/10/06, Gianny Damour [EMAIL PROTECTED] wrote:
Hi Manu,Manu George wrote: Hi , I am also not sure if this is a safe behaviour or even whether the
Hi Manu,
Manu George wrote:
Hi ,
I am also not sure if this is a safe behaviour or even
whether the ejb spec requires it. I have seen in a particular sun
forum that the pk should not be part of any relation.
I have put the link below
Hi ,
I am also not
sure if this is a safe behaviour or even whether the ejb spec requires
it. I have seen in a particular sun forum that the pk should not be
part of any relation.
I have put the link below
http://archives.java.sun.com/cgi-bin/wa?A2=ind0203L=ejb-interestF=S=P=22402.
If this is
Hi Manu,
You are once again correct: let's remove this read-only decorator - this
was a very bad idea - at least if the field is a PK one. This read only
behavior was intended to prevent developers from changing a relationship
to a CMP having a coumpond PK with multiple fields. Indeed, in
Hi Gianny,
I have a question on CMR
Consider a Bean A and a bean B in a one to many CMR relationship
Here A has 2 fields in the PK say a1 and a2
B has b1 fka1 and fka2 as the pk where fka1 and fka2 are the foreign
keys corressponding to the a1 and a2 of A.
In
the ejbCreate of B when we set
