That is because remove() operates on the particular instance. For example,
in Entity beans, if you call remove() you will be deleting the specific
entity on which it is called. Since you can't be talking to more than one
instance at a time, you can't delete more than one at a time.
If you want to have a 'mass deletion' routine, I would put it in a Session
bean. That bean could take all of the parameters required for the delete,
and then perform a delete as a single line of SQL.
Jonathan Baker
Raj Sekhar wrote:
>
> hi all,
>
> we have multiple finder methods, where u can have
> multiple ejbObjects as the return type. And we have
> remove method also in home interface, but if i want to
> remove more than one bean from the container it's not
> possible,since the specification did not mention
> regarding that functionality.
>
> my question is..
>
> What could be the problem if they defined multiple
> delete methods in the Home interface? Is that a
> performance issue or any design stratagy?
>
> thanx in advance
>
> bye
>
> Raj
>
> __________________________________________________
> Get personalized email addresses from Yahoo! Mail - only $35
> a year! http://personal.mail.yahoo.com/
>
> ===========================================================================
> 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".
--
Jonathan Baker
Senior Architect
Internet Applications Division
Sybase, Inc.
[EMAIL PROTECTED]
+1 510 922-0460
===========================================================================
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".
