After being directed to an obscure section (4.3) of the EJB release notes
for VisualAge 3.02EE, the problem has been resolved. Incidentally, those
notes do recommend passing the remote associated object rather than its
primary key.
The solution is IBM-specific, including modifying both ejbCreate (to extract
the associated object's primary key) and ejbPostCreate (which discards the
primary key just obtained, then finally sets the associated instance
itself).
After giving the example, the notes state "In a future release, we may
provide a more logical solution... for now, this is the way it must be
coded."
Charles May, Programmer/Analyst
AFCO Credit Corp. - Pittsburgh Systems Group
A Mellon Financial Company
(The views represented in this message are my own, and do not necessarily
represent the views of my employer).
===========================================================================
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".
