Moreover if the methods are public and still not added in remote interface, the application will still not able to use these methods. You need to have them in remote interface to use except while extending the session bean class itself.
warm regards Salil Malhotra -----Original Message----- From: Salil Malhotra-OP Sent: Friday, April 04, 2003 2:56 PM To: 'linesofcode' Cc: '[EMAIL PROTECTED]' Subject: RE: Re: Keep the methods private or make them public and not adding inRemote interface Hi! Yeah you are right! but that decision is Application Specific. I wanted to ask does that make any difference in performance or any Container Issues? Salil Malhotra -----Original Message----- From: linesofcode [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 2:43 PM To: [EMAIL PROTECTED] Subject: Re: Keep the methods private or make them public and not adding inRemote interface Hi, Sometimes you may have classes in your application whose methods may internally use the methods of the some other class. Making the methods private would make this impossible. The second alternative enables the above but at the same time hides them from the client. Methods which are used internally by methods of the bean can have such visibility. With best regards, 88 Deg East ============================================ Hi All ! What is the difference in the making the Session Beans methods (1) Private (2) Keeping them public and not promoting these public methods to the Remote interface. I have been always using the first way but got confused after a long time of the need for the same. I have seen the classes generated by the container and there is no difference in these classes after using either way. Regards Salil Malhotra DISCLAIMER: This message contains privileged and confidential information and is intended only for the individual named.If you are not the intended recipient you should not disseminate,distribute,store,print, copy or deliver this message.Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted,corrupted,lost,destroyed,arrive late or incomplete or contain viruses.The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the bodyof 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". DISCLAIMER: This message contains privileged and confidential information and is intended only for the individual named.If you are not the intended recipient you should not disseminate,distribute,store,print, copy or deliver this message.Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted,corrupted,lost,destroyed,arrive late or incomplete or contain viruses.The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. ==========================================================================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".
