I think a servlet is a more appropriate server extension vehicle than a
bean, since servlets have squarely dealt with lifecycle management, service
invocation, and reaching into the host process for configuration
properties. I wonder if "EjbServlet extends Servlet" (not HttpServlet!!)
is closer to what you're looking for.
David
Wei Jiang <[EMAIL PROTECTED]> on 08/30/99 06:37:47 PM
Please respond to A mailing list for Enterprise JavaBeans development
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: David Rauschenbach/ZLAND)
Subject A proposal: Component Based Extension
: Architecture for EJB Server
Note: Some recipients have been dropped due to syntax errors.
Please refer to the "$AdditionalHeaders" item for the complete headers.
A proposal:
Component Based Extension Architecture for EJB Server
Draft 1
Auther: Wei Jiang <[EMAIL PROTECTED]>
Comments are welcome.
The Architecture
This architecture intents to be powerful, flexible and
simple.
1. Each extension is a regular Java Bean in a jar
file, called a
ServerBean. It can have other supporting files with
it, in the
same jar or as separated files. The ServerBean is
resposible to
load related files. The server may or may not know
what a
ServerBean does. The server only manages its life
cycle.
2. All extension jar files and related files reside
under
Extension Directory, such as
SERVER_HOME/classes/ext or
SERVER_HOME/lib/ext
3. The server runs a class named ForeignAffairs when
it starts.
ForeignAffairs loads all installed ServerBeans.
ForeignAffairs
registers itself with the server. Both the server and
remote
administration tools can invoke ForeignAffairs.
4. ForeignAffairs gets the list of installed
ServerBeans as a
parameter of its method call. The list of installed
ServerBeans
originaly comes from a properties file. A property
named
ExtensionClasses is defined in the properties file.
The value
of ExtensionClasses is a comma separated string. This
is the content
of extension classes. Each part of it is a full class
name, the
class name for the ServerBeans. The .class resides in
a jar file
under Extension Directory.
5. ForeignAffairs quiently ignore all exceptions from
ServerBeans:
it does not know how to handle them.
6. Each ServerBean implements ServerBeanInterface.
7. ForeignAffairs registers each ServerBean, so the
server or remote
administation tools can start or shutdown each
ServerBean.
The ServerBeanInterface
Each ServerBean provides a public constructor with no
parameters.
This constructor is responsible for starting the bean.
ServerBeanInterface is more approperiate than
java.Beans and
related classes are mainly for visible beans.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I plan to contribute an implementation on Jonas EJB
server very soon.
The contrubution will include:
1. Necessary code for loading extensions as core of
Jonas.
2. An example to show that a ServerBean is an
extension of Jonas.
I am writing a remote administration tool in Swing
which is
component based tool. I may add more things on Jonas
and other
EJB servers, as long as they are open enough (in Java
way)
for me to do so.
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
===========================================================================
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".
===========================================================================
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".
