I also agree with alex. We can use direct DELETE commands through session beans for mass delete. We are also using this in our application. But it also deviates from the point that u should access ur database using ejbs only. code modularity destroys and maintenace is not easy in this case.
Also there are two things :- 1. If your client is a normal java class (not residing on the same machine on which EJB is running) then this approach is better because it will reduce the remote procedural call overhead and other ejb load/store etc. 2. On the other hand if ur client is a JSP page, residing on the same machine on which EJB is running, then there wont be much difference performancewise because container uses a proxy object for invoking ejb methods in this case and does not consider as remote call. Regards Mohit =========================================================================== 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".
