Hi All,
An EJB application server constantly listen for serving a client for
accessing the deployed beans & get their work done.Is this the only
listening activity the server should do?Can't an application server
listen for deploying a new bean in it's pool?Deploying an EJBean at
runtime would further increase the distributed functionality of an
application server.If the priveleged access for such client is possible
then there will be many possible benifit like :
* A small enterprise who want to use the EJB application need not have
to purchase an application server.
* Shutting down the system for deploying the bean will not be needed.
* Frequent maintaining the EJB application will be at ease.
I would like to read the views from the EJB gurus.
Nittile.
===========================================================================
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".
