Nilofer,
What EJB server are you using? If it's based on Java RMI such as WebLogic,
you can probably count on downloadable classes as needed. If it's based on
CORBA, you need to deploy the stubs yourself, since CORBA does not support
downloadable classes. In any scenario, you're definately going to need the
following files on the client before you do any work with EJB:
- The bean's home interface
- The bean's remote interface
For performance, you could deploy the stubs as well as the interfaces.
However, this may become a maintenance problem if you need to switch EJB servers
(all client apps need to be re-deployed).
--
Hi,
I am new to enterprise JavaBeans. My question which files should the
client have on his side? Is it enough when the client application
resides on the client, and then by creating a instance of the Bean, he
gets the appropriate stub-file for that bean.
Please help me,
Nilofer Popal
===========================================================================
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".
