Sorry for my wrong assumption, but then what I said would not help you much.
Deferred keys are specified at the time of deployment. Section 9.4.7 of
EJB1.1 spec will give you good idea on this.
Hemant
www.pramati.com
----- Original Message -----
From: "David M. Karr" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 06, 2001 9:57 AM
Subject: Re: PK for entity which has refs to other entities?
>>>>> "Hemant" == Hemant Khandelwal <[EMAIL PROTECTED]> writes:
Hemant> Hi David,
Hemant> I think primary key for "StudentClassGrade" would be best
modelled as
Hemant> deferred key, if your clients do not use explicit knowledge of
both "ssn"
Hemant> and "name" in the same method. (for example in
findByPrimaryKey(Object)).
Hemant> You can specify the primary key type as java.lang.Object in the
deployment
Hemant> descriptor.
I'm sorry, I have no idea what you mean by this. Could you please
elaborate?
Hemant> I am assuming that you are using CMP2.0 entity beans. In that
case, the
Hemant> primary keys at the persistent store will be updated whenever
the
Hemant> relationship between "Student" and "Class" is associated /
dissociated by
Hemant> the container.
Why do you assume I'm using 2.0? I'm not.
--
===================================================================
David M. Karr ; Best Consulting
[EMAIL PROTECTED] ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
