Hey
I can comment on behalf of the EJBoss project (http://www.ejboss.org).
Nittle Gupta wrote:
> 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.
This will be a possibility if the features you outline are implemented,
yes. ASP's (Application Service Providers) will be the natural evolution
of the functions of ISP's today. It will happen within 1-2 years IMHO.
> * Shutting down the system for deploying the bean will not be needed.
EJBoss have this feature today. :-) This is rather tricky and I don't
know of any other server that supports this properly. AFAIK some are
unable to unload the bean code, but I'm not sure how other servers
handle interface(/"contract") classes such as remote interfaces and data
holder classes.
> * Frequent maintaining the EJB application will be at ease.
Yes, easy maintenance is a must. Not having to shut down the server each
and every time is a big step in the right direction.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
