Jon,
Option 'None'. OK. So you would not have any problems with a container
returning a remote reference to an entity bean that does not exist in the
database. Only when you call a business method on the remote will you client
detect the error. This will result in confusing client exception handling
code. Would it not be easier to have already captured this exception and
reported it prior to normal business method invocations. The only time that
this would be benefical (optimization i.e. no verification sql statement)
would be when you were assured that the primary key did exist in the
database at the time of transactional work. Unless the primary key was
obtained in the same transaciton there really is no assurance since many
transactions could be executing simulatenously in any number of processes
both ejb and 'non-ejb' based.
regards,
William Louth
Borland/Inprise
www.inprise.com/appserver
-----Original Message-----
From: Jon Finanger [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 22, 2000 6:13 AM
To: [EMAIL PROTECTED]
Subject: Re: findByPrimaryKey spec. question
> I personally would also prefer to know
> first off if the object I am trying to access still exists especially if I
> am using a PK to obtain a reference to it.
why would would that be neccesary?
The only situation i can think of this beeing 'neccesary' is if a non-ejb
client deletes the database record. Agree?
/Jon
===========================================================================
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".
